Triple
T10029229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio–Niterói Bridge |
E204809
|
entity |
| Predicate | navigationSpanLength |
P91782
|
FINISHED |
| Object | about 300 metres |
—
|
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 300 metres | Statement: [Rio–Niterói Bridge, navigationSpanLength, about 300 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSpanLength Context triple: [Rio–Niterói Bridge, navigationSpanLength, about 300 metres]
-
A.
hasNavigationSpan
Indicates that one entity includes or is associated with a specific navigational range or segment used for movement or routing.
-
B.
numberOfSpans
Indicates the total count of distinct spans or segments associated with an entity or within a specified context.
-
C.
largestSpan
Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
-
D.
leafSpan
Indicates the extent or range covered by a leaf, such as its length, width, or overall spread.
-
E.
archSpan
Indicates the distance or extent between the supports of an arch, typically measured horizontally from one side to the other.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcde69bd08190a5c79ec8487dfff6 |
completed | April 2, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:54 p.m.