Triple
T24976454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raleigh Chopper |
E625034
|
entity |
| Predicate | wasReintroduced |
P65312
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Raleigh Chopper, wasReintroduced, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasReintroduced Context triple: [Raleigh Chopper, wasReintroduced, 2004]
-
A.
laterReintroducedBy
Indicates that something previously removed, discontinued, or absent was brought back or reinstated at a subsequent time by a specified agent or entity.
-
B.
reintroduced
Indicates that an entity that was previously removed, extinct, or absent has been brought back or restored to a place, context, or state.
-
C.
reintroducedFrom
Indicates that an entity has been brought back or restored from a specified prior source, context, or location after having been removed, lost, or discontinued.
-
D.
reintroducedInYear
chosen
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
E.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:02 a.m.