Triple
T8718591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont Saint-Louis |
E206955
|
entity |
| Predicate | hasPreviousStructureCount |
P64710
|
FINISHED |
| Object | several earlier bridges |
—
|
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: several earlier bridges | Statement: [Pont Saint-Louis, hasPreviousStructureCount, several earlier bridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreviousStructureCount Context triple: [Pont Saint-Louis, hasPreviousStructureCount, several earlier bridges]
-
A.
hasStructureCount
chosen
Indicates the number of structures associated with or contained by a given entity.
-
B.
hasStructureAbove
Indicates that one entity has another entity positioned vertically higher or located on top of it within a structural or spatial arrangement.
-
C.
hasPredecessorStructureFrom
Indicates that one structure existed or was established before another structure in a sequential or developmental order.
-
D.
previousStructure
Indicates that one structure directly precedes another in a defined sequence or configuration.
-
E.
hasVersionCount
Indicates the total number of distinct versions associated with a given 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d014e208190a4c6055901580d0c |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.