Triple
T26648724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlands Checkpoint |
E668990
|
entity |
| Predicate | otherMainCheckpoint |
P167098
|
FINISHED |
| Object | Tuas Checkpoint |
—
|
NE NERFINISHED |
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: Tuas Checkpoint | Statement: [Woodlands Checkpoint, otherMainCheckpoint, Tuas Checkpoint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherMainCheckpoint Context triple: [Woodlands Checkpoint, otherMainCheckpoint, Tuas Checkpoint]
-
A.
otherMainBridge
Indicates that one bridge serves as an alternative or secondary primary bridge in relation to another main bridge.
-
B.
otherMainCorridor
Indicates that one corridor is an alternative or secondary main corridor relative to another within the same structure or network.
-
C.
otherMainEid
Indicates that an entity is associated with another primary entity identifier, linking it as an alternate or secondary main reference.
-
D.
laterLocation
Indicates that an entity is located at a specified place at a later time than some reference time or earlier location.
-
E.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
- 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 2:32 a.m.