Triple
T8588110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leguan bridge-layer |
E203358
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military bridge-layer system |
C24681
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: military bridge-layer system Context triple: [Leguan bridge-layer, instanceOf, military bridge-layer system]
-
A.
toll bridge system
A toll bridge system is a coordinated set of hardware, software, and procedures that manages vehicle identification, fee calculation, payment processing, and access control for crossing a bridge.
-
B.
bridge network
A bridge network is a system of interconnected bridges and links that provides multiple paths for traffic or data to travel between nodes, enhancing reliability and load distribution.
-
C.
defensive avionics system
A defensive avionics system is an integrated suite of onboard sensors, processors, and countermeasure devices designed to detect, identify, and protect an aircraft from hostile threats such as radar, missiles, and electronic attacks.
-
D.
military radar system
A military radar system is an integrated sensor platform that emits and receives electromagnetic signals to detect, track, and classify airborne, maritime, or ground targets for surveillance, targeting, and defense operations.
-
E.
through-arch bridge
A through-arch bridge is a type of arch bridge in which the deck passes between the arches, with the arch ribs rising above the roadway and connected by vertical or diagonal hangers that support the deck.
- F. None of above. chosen
Provenance (1 batch)
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. |
Created at: March 30, 2026, 6:23 p.m.