Triple
T32327945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A413 road bridges |
E825964
|
entity |
| Predicate | hasNumberOfStructures |
P64710
|
FINISHED |
| Object | multiple |
—
|
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: multiple | Statement: [A413 road bridges, hasNumberOfStructures, multiple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfStructures Context triple: [A413 road bridges, hasNumberOfStructures, multiple]
-
A.
hasStructureCount
chosen
Indicates the number of structures associated with or contained by a given entity.
-
B.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
C.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
-
D.
hasSignificantStructure
Indicates that an entity possesses a structure or internal organization that is notably complex, important, or meaningful in a given context.
-
E.
hasStructureLevel
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
- F. None of above.
Provenance (3 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: May 1, 2026, 12:47 a.m.