Triple
T3222104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athens Metro |
E67533
|
entity |
| Predicate | modernNetworkOpening |
P46617
|
FINISHED |
| Object | 2000 |
—
|
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: 2000 | Statement: [Athens Metro, modernNetworkOpening, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernNetworkOpening Context triple: [Athens Metro, modernNetworkOpening, 2000]
-
A.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
B.
openingConcept
Indicates that one concept serves as the initial or introductory element in relation to another concept, such as the first idea, section, or phase in a sequence or structure.
-
C.
typicalOpeningPattern
Indicates that there is a commonly occurring or characteristic initial configuration, sequence, or arrangement associated with the given context.
-
D.
openingTheme
Indicates that one entity serves as the opening theme (such as a song or musical piece) for another entity, typically a show, series, or similar work.
-
E.
homeFieldOpened
Indicates that a team's designated home field has officially begun operation or been opened for use.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1845408190b3eccd791231c69c |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:08 p.m.