Triple
T34128412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | d’Eyquem |
E875356
|
entity |
| Predicate | usedAsComponentOfName |
P32965
|
FINISHED |
| Object | Michel Eyquem de Montaigne |
—
|
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: Michel Eyquem de Montaigne | Statement: [d’Eyquem, usedAsComponentOfName, Michel Eyquem de Montaigne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsComponentOfName Context triple: [d’Eyquem, usedAsComponentOfName, Michel Eyquem de Montaigne]
-
A.
isComponentOfNameOf
Indicates that one entity is the name of a component or part belonging to another entity.
-
B.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
C.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
usedInFullNameOf
chosen
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
E.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
- 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_69f349aa33848190a2e6c5e4533c8444 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:53 a.m.