Triple
T26072163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Servatius Bridge |
E657578
|
entity |
| Predicate | hasConstructionForm |
P44411
|
FINISHED |
| Object | masonry arches |
—
|
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 arches | Statement: [Saint Servatius Bridge, hasConstructionForm, masonry arches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstructionForm Context triple: [Saint Servatius Bridge, hasConstructionForm, masonry arches]
-
A.
hasConstruction
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
B.
hasBuildingForm
chosen
Indicates that an entity possesses or is characterized by a particular architectural or structural building form.
-
C.
hasFormed
Indicates that an entity has come together or been created into a particular structure, group, or configuration.
-
D.
isFormedFor
Indicates that something is created, established, or brought into existence for a particular purpose, function, or beneficiary.
-
E.
hasFormationComponent
Indicates that something is a constituent part or element involved in the formation or construction 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 26, 2026, 7:30 p.m.