Triple
T2991281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puente de San Martín |
E80756
|
entity |
| Predicate | isBuiltType |
P841
|
FINISHED |
| Object | masonry arch bridge |
—
|
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: masonry arch bridge | Statement: [Puente de San Martín, isBuiltType, masonry arch bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBuiltType Context triple: [Puente de San Martín, isBuiltType, masonry arch bridge]
-
A.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
B.
hasStructureType
chosen
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
isLargestTypeOf
Indicates that one entity represents the largest variant, category, or instance within a specified type or group relative to others.
-
D.
builtInTypeCategory
Indicates that one type is classified under a particular built-in type category (such as numeric, string, or boolean).
-
E.
hasStandardType
Indicates that something conforms to or is categorized under a defined standard classification or type.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99df69d08190a0e25efb0dc8d653 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.