Triple
T35967855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Po Lam station |
E1040192
|
entity |
| Predicate | hasConcourseLocation |
P207116
|
FINISHED |
| Object | at ground level |
—
|
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: at ground level | Statement: [Po Lam station, hasConcourseLocation, at ground level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConcourseLocation Context triple: [Po Lam station, hasConcourseLocation, at ground level]
-
A.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
B.
hasFacilityLocation
Indicates that an entity possesses or is associated with a facility situated at a specific location.
-
C.
hasMeetingLocation
Indicates that an entity (such as a meeting or event) takes place at or is associated with a specific location.
-
D.
hasActLocation
Indicates that an action or event occurs at, or is associated with, a specific location.
-
E.
hasLocationsIn
Indicates that an entity maintains a presence, operations, or facilities in one or more specified geographic locations.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.