Triple
T19791596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pont de Mirabeau |
E475423
|
entity |
| Predicate | architecte |
P6475
|
FINISHED |
| Object | Jean Résal |
—
|
NE NERFINISHED |
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: Jean Résal | Statement: [Pont de Mirabeau, architecte, Jean Résal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architecte Context triple: [Pont de Mirabeau, architecte, Jean Résal]
-
A.
coArchitectOf
Indicates a relationship where two or more entities jointly serve as architects of the same project, design, or structure.
-
B.
architecturalRole
Indicates the functional or design-related role that one entity plays within the structure, layout, or organization of another entity.
-
C.
architecturalPlanner
chosen
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of another entity.
-
D.
supervisingArchitect
Indicates that one entity serves as the overseeing architect responsible for directing, reviewing, or approving the architectural work of another entity or project.
-
E.
architecturalCollaborator
Indicates a relationship where one entity works jointly with another on architectural design, planning, or related architectural activities.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653c37a3c819080f195d58adaaa7b |
completed | April 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.