Triple
T38574635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Penang Bridge |
E929366
|
entity |
| Predicate | lengthOverWater |
P191208
|
FINISHED |
| Object | about 16.9 km |
—
|
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: about 16.9 km | Statement: [Second Penang Bridge, lengthOverWater, about 16.9 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthOverWater Context triple: [Second Penang Bridge, lengthOverWater, about 16.9 km]
-
A.
waterwayLengthKilometres
Indicates the total length of a waterway, measured in kilometres.
-
B.
lengthUnderseaSection
Indicates that the specified length pertains to the portion of an object or route that lies beneath the sea surface.
-
C.
distanceToLand’sEnd
Indicates the measured distance between a given location or object and the specific place referred to as Land’s End.
-
D.
hasApproachOverWater
Indicates that the approach to a location or object involves traveling over a body of water.
-
E.
waterbodyOnCourse
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.