Triple
T16751282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurilpa Bridge |
E407085
|
entity |
| Predicate | hasNumberOfCables |
P124497
|
FINISHED |
| Object | over 500 |
—
|
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: over 500 | Statement: [Kurilpa Bridge, hasNumberOfCables, over 500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCables Context triple: [Kurilpa Bridge, hasNumberOfCables, over 500]
-
A.
hasNumberOfMainCables
Indicates the quantity of primary cables associated with or used by an entity.
-
B.
isTypicallyWiredUsing
Indicates that one thing is commonly connected or implemented using a particular type of wiring or cabling.
-
C.
hasCableArrangement
Indicates that one entity is connected to or equipped with another entity through a specific configuration or layout of cables.
-
D.
cableLength
Indicates the physical length of a cable connecting or associated with an entity.
-
E.
numberOfWires
Indicates the quantity of wires associated with or contained in a given entity.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa271de48190b4a535408aeef734 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.