Triple
T6920197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogor dell’Amore |
E160162
|
entity |
| Predicate | bridgesWorldsBetween |
P2535
|
FINISHED |
| Object | Renaissance Florence |
—
|
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: Renaissance Florence | Statement: [Mogor dell’Amore, bridgesWorldsBetween, Renaissance Florence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgesWorldsBetween Context triple: [Mogor dell’Amore, bridgesWorldsBetween, Renaissance Florence]
-
A.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
B.
bridges
chosen
Indicates that one entity connects or links two or more other entities, allowing passage, transition, or interaction between them.
-
C.
bridged
Indicates that one entity has formed a connection or link that spans across or over another entity, effectively joining two previously separated points.
-
D.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
E.
hasNumberOfBridges
Indicates the quantitative relationship specifying how many bridges are 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_69c6883ab1008190a07129ff06f625d9 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d9fa452c8190b2bea2d47309c889 |
completed | March 27, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b93d688190a297244ce81b67ac |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:26 p.m.