Triple
T11213281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertrand-Jean Redon |
E265362
|
entity |
| Predicate | knownAsBridgeBetween |
P97873
|
FINISHED |
| Object | 19th-century symbolism |
—
|
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: 19th-century symbolism | Statement: [Bertrand-Jean Redon, knownAsBridgeBetween, 19th-century symbolism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownAsBridgeBetween Context triple: [Bertrand-Jean Redon, knownAsBridgeBetween, 19th-century symbolism]
-
A.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
B.
bridgeName
Indicates the designated name assigned to a specific bridge.
-
C.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
D.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
E.
bridged
Indicates that one entity has formed a connection or link that spans across or over another entity, effectively joining two previously separated points.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d7f47c8190b78c640ff1a01943 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.