Triple
T24298395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Chapman |
E606027
|
entity |
| Predicate | activeInBandFrom |
P113374
|
FINISHED |
| Object | New Order – 2011 |
—
|
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: New Order – 2011 | Statement: [Tom Chapman, activeInBandFrom, New Order – 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeInBandFrom Context triple: [Tom Chapman, activeInBandFrom, New Order – 2011]
-
A.
activeInBandSince
chosen
Indicates that an entity has been an active member of a band starting from a specified point in time.
-
B.
activeInBand
Indicates that an entity is a current member performing or participating in the activities of a specific band.
-
C.
activeFrom
Indicates the starting point in time from which an entity or relationship is considered active or in effect.
-
D.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
-
E.
activeInFieldFrom
Indicates that an entity is professionally or actively engaged in a particular field starting from a specified point in time.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f2915c520081908055941209f35da5 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 12:09 a.m.