Triple
T32907708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Pont de l’Europe |
E841785
|
entity |
| Predicate | depictsStructureType |
P125859
|
FINISHED |
| Object | railway 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: railway bridge | Statement: [Le Pont de l’Europe, depictsStructureType, railway bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depictsStructureType Context triple: [Le Pont de l’Europe, depictsStructureType, railway bridge]
-
A.
depictsBuildingType
chosen
Indicates that one entity visually represents or portrays a specific type or category of building associated with another entity.
-
B.
designedStructureType
Indicates the type or category of structure that something has been specifically designed to be.
-
C.
depictionType
Indicates the specific manner or style in which something is visually represented or depicted.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
showsStructure
Indicates that one entity visually or conceptually presents the internal organization, arrangement, or composition 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 1, 2026, 1:19 a.m.