Triple
T9736470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portsmouth North |
E236075
|
entity |
| Predicate | MPsince |
P90733
|
FINISHED |
| Object | 2010 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2010 | Statement: [Portsmouth North, MPsince, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MPsince Context triple: [Portsmouth North, MPsince, 2010]
-
A.
PSE
Indicates a relationship where one entity is engaged in or associated with a public service or public sector employment role relative to another entity or context.
-
B.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
-
C.
metOn
Indicates that two or more entities encountered each other at the same time and place for the first time or for a particular meeting.
-
D.
MOSCode
Indicates a relationship where a specific Military Occupational Specialty (MOS) code is assigned to or associated with an entity, such as a person, position, or role.
-
E.
mpcNumber
Indicates that an entity is associated with a specific MPC (Manufacturer Part Code or similar standardized catalog) identification number.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef032088190acd94c35b89e48b7 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd07c5c978819084abc7267a5ced80 |
completed | April 1, 2026, 11:55 a.m. |
Created at: March 30, 2026, 8:22 p.m.