Triple
T30171280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G |
E766926
|
entity |
| Predicate | renamedToSingleLetterServices |
P50535
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [G, renamedToSingleLetterServices, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renamedToSingleLetterServices Context triple: [G, renamedToSingleLetterServices, 1979]
-
A.
serviceRenamedAs
chosen
Indicates that a service previously known by one name is now identified or referred to by a different name.
-
B.
shortenedInService
Indicates that an entity’s length, duration, or extent has been reduced as a result of its use or operation in service.
-
C.
expressServiceName
Indicates that a service is identified or labeled by a specific express (fast or priority) service name.
-
D.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
E.
relocatedAndRenamed
Indicates that an entity has moved from one location to another and changed its name as part of that move.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0c2d248190a12c361305d6f00d |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:24 p.m.