Triple
T8109329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploiești Sud railway station |
E189306
|
entity |
| Predicate | hasApproximateOpeningCentury |
P10255
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Ploiești Sud railway station, hasApproximateOpeningCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOpeningCentury Context triple: [Ploiești Sud railway station, hasApproximateOpeningCentury, 20th century]
-
A.
openedInCentury
chosen
Indicates that an entity (such as a building, institution, or facility) began operating or was first opened during a specified century.
-
B.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
C.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
D.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
E.
attestedUntilCentury
Indicates the latest century up to which the existence or use of something is historically documented or evidenced.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4664fef881908b0dc7b158aca398 |
completed | March 31, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69cb368e7f4c81909aabd7716f0de79d |
completed | March 31, 2026, 2:50 a.m. |
Created at: March 30, 2026, 5:32 p.m.