Triple
T36857257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Lambert Port A |
E910829
|
entity |
| Predicate | railHeadsAt |
P110961
|
FINISHED |
| Object | Cape Lambert Port A |
—
|
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: Cape Lambert Port A | Statement: [Cape Lambert Port A, railHeadsAt, Cape Lambert Port A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railHeadsAt Context triple: [Cape Lambert Port A, railHeadsAt, Cape Lambert Port A]
-
A.
railHead
chosen
Indicates a relationship where one location serves as the terminus or primary endpoint of a railway line for another location or transport link.
-
B.
railTerminus
Indicates that a railway line or service ends at a particular station or location, which serves as its final terminus.
-
C.
railroadTerminusFor
Indicates that one location serves as the end point or final station of a particular railroad line for another location.
-
D.
hasRailStation
Indicates that one entity possesses, contains, or is served by a rail station.
-
E.
railTerminusFor
Indicates that one location serves as the final or terminal rail station or endpoint for a specified rail line or service.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.