Triple
T1647008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clayton Hall tram stop |
E35603
|
entity |
| Predicate | zoneSystemIntroduced |
P30843
|
FINISHED |
| Object | 2019-01-13 |
—
|
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: 2019-01-13 | Statement: [Clayton Hall tram stop, zoneSystemIntroduced, 2019-01-13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoneSystemIntroduced Context triple: [Clayton Hall tram stop, zoneSystemIntroduced, 2019-01-13]
-
A.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
-
B.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
C.
hasNumberOfNationalTimeZones
Indicates the quantity of distinct official time zones that a nation or country uses within its territory.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
- 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a949509d508190a3a35554996823de |
completed | March 5, 2026, 9:13 a.m. |
Created at: March 4, 2026, 7:28 p.m.