Triple
T7619202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BEAR Scotland |
E172444
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road maintenance company |
C2979
|
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: road maintenance company Context triple: [BEAR Scotland, instanceOf, road maintenance company]
-
A.
bridge construction company
A bridge construction company is a specialized engineering and construction firm that plans, designs, and builds bridges, managing all phases from feasibility studies and structural design to on-site construction and maintenance.
-
B.
toll road operator
A toll road operator is an entity responsible for managing, maintaining, and collecting user fees on designated roadways or bridges, often under government concession or private ownership.
-
C.
road infrastructure
Road infrastructure encompasses the physical structures, systems, and facilities—such as roads, bridges, tunnels, signage, and drainage—designed and built to support safe and efficient vehicular and pedestrian transportation.
-
D.
infrastructure management company
chosen
An infrastructure management company plans, operates, maintains, and optimizes physical assets and systems—such as transportation, utilities, and public works—to ensure their reliability, efficiency, and long-term performance.
-
E.
construction management firm
A construction management firm is a professional organization that plans, coordinates, and oversees construction projects from inception to completion, ensuring they are delivered on time, within budget, and to specified quality and safety standards.
- F. None of above.
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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
Created at: March 27, 2026, 3:55 p.m.