Triple
T31281677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pickering A |
E797686
|
entity |
| Predicate | statusOfUnit1 |
P35303
|
FINISHED |
| Object | in operation (after refurbishment) |
—
|
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: in operation (after refurbishment) | Statement: [Pickering A, statusOfUnit1, in operation (after refurbishment)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusOfUnit1 Context triple: [Pickering A, statusOfUnit1, in operation (after refurbishment)]
-
A.
hasUnitStatus
chosen
Indicates that an entity is associated with a particular operational or condition status as a unit.
-
B.
statusOfSubunit
Indicates the current condition, state, or operational situation of a component or subunit in relation to its larger whole.
-
C.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
D.
classStatus
Indicates the current academic or enrollment standing of an entity within a class or course context.
-
E.
statusInUMC
Indicates that an entity holds a particular status or standing within the UMC (e.g., United Methodist Church) context.
- F. None of above.
Provenance (3 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 9:13 p.m.