Triple
T15600946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ásbrú |
E375029
|
entity |
| Predicate | structuralDescription |
P62440
|
FINISHED |
| Object | three-colored 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: three-colored bridge | Statement: [Ásbrú, structuralDescription, three-colored bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralDescription Context triple: [Ásbrú, structuralDescription, three-colored bridge]
-
A.
designDescription
Indicates that an entity has a textual explanation or summary of its design, structure, or intended configuration.
-
B.
materialDescribedAs
Indicates that a material is characterized or specified using a particular descriptive term, label, or textual description.
-
C.
structuralAmbition
Indicates an entity’s intention or effort to change, shape, or influence an existing structure, system, or organizational framework.
-
D.
typicalStructuralElement
Indicates that one entity is a standard or characteristic structural component commonly found within or forming part of another entity.
-
E.
surfaceDescription
chosen
Indicates that one entity provides a textual or qualitative description of the surface characteristics or appearance of another entity.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e621fc4819097e8e85e7ddfdc6c |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.