Triple
T35547007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mei Foo station |
E1027245
|
entity |
| Predicate | tuenMaLineThroughRunningDate |
P183400
|
FINISHED |
| Object | 2021-06-27 |
—
|
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: 2021-06-27 | Statement: [Mei Foo station, tuenMaLineThroughRunningDate, 2021-06-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tuenMaLineThroughRunningDate Context triple: [Mei Foo station, tuenMaLineThroughRunningDate, 2021-06-27]
-
A.
lineThrough
Indicates that a straight geometric line passes through or intersects the referenced entity or set of entities.
-
B.
fullThroughRunningDate
Indicates that something remains fully valid, active, or in effect up to and including a specified running (end) date.
-
C.
scanLineCorrectorFailureDate
Indicates the date on which a scan line corrector experienced or was recorded as having a failure.
-
D.
completionDateMainLine
Indicates the date on which the primary or main phase of an activity, project, or process is completed.
-
E.
runoffDate
Indicates the date on which a runoff event (such as a runoff election or runoff water occurrence) takes place or is scheduled.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:04 p.m.