Triple
T8588140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leguan bridge-layer |
E203358
|
entity |
| Predicate | bridgeCapacity |
P83735
|
FINISHED |
| Object | suitable for main battle tank weight classes in many configurations |
—
|
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: suitable for main battle tank weight classes in many configurations | Statement: [Leguan bridge-layer, bridgeCapacity, suitable for main battle tank weight classes in many configurations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeCapacity Context triple: [Leguan bridge-layer, bridgeCapacity, suitable for main battle tank weight classes in many configurations]
-
A.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
B.
bridgeLength
Indicates the physical length or span of a bridge structure.
-
C.
bridgeSpans
Indicates that a bridge extends across and connects two separate points or areas.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
bridgeOpened
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:23 p.m.