Triple
T26272181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogier de le Pasture |
E660451
|
entity |
| Predicate | convertedNameTo |
P157853
|
FINISHED |
| Object | Rogier van der Weyden |
—
|
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: Rogier van der Weyden | Statement: [Rogier de le Pasture, convertedNameTo, Rogier van der Weyden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedNameTo Context triple: [Rogier de le Pasture, convertedNameTo, Rogier van der Weyden]
-
A.
conversionName
Indicates that one entity is the name or label assigned to a specific conversion event or conversion process associated with another entity.
-
B.
changesNameTo
chosen
Indicates that an entity alters its current name and adopts a new specified name.
-
C.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
D.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
E.
convertedFor
Indicates that one entity has been transformed, adapted, or reformatted specifically for use, compatibility, or suitability with 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 9:51 p.m.