Triple
T29511633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandoyartunnilin |
E748668
|
entity |
| Predicate | hasStructureGauge |
P195350
|
FINISHED |
| Object | road tunnel profile |
—
|
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: road tunnel profile | Statement: [Sandoyartunnilin, hasStructureGauge, road tunnel profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStructureGauge Context triple: [Sandoyartunnilin, hasStructureGauge, road tunnel profile]
-
A.
haveStructure
Indicates that an entity possesses a particular internal organization, arrangement, or structural composition.
-
B.
hasStructureCount
Indicates the number of structures associated with or contained by a given entity.
-
C.
hasStructureLevel
Indicates a relationship where one entity possesses, is assigned, or is characterized by a particular structural level within a hierarchy or layered organization.
-
D.
hasStructuralCharacter
Indicates that one entity possesses a particular structural property, form, or configuration that characterizes it.
-
E.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
- F. None of above. chosen
Provenance (4 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69fdbc5da9988190b95234bce4cc2062 |
completed | May 8, 2026, 10:35 a.m. |
Created at: April 28, 2026, 4:33 p.m.