Triple
T28772771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | du Manoir |
E726455
|
entity |
| Predicate | hasDerivativeName |
P191685
|
FINISHED |
| Object | Stade Yves-du-Manoir |
—
|
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: Stade Yves-du-Manoir | Statement: [du Manoir, hasDerivativeName, Stade Yves-du-Manoir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivativeName Context triple: [du Manoir, hasDerivativeName, Stade Yves-du-Manoir]
-
A.
hasDerivative
Indicates that one entity is derived, obtained, or produced from another through some transformation, process, or modification.
-
B.
hasDerivativeCharacter
Indicates that one character is derived, adapted, or developed from another character.
-
C.
hasDerivativeTerm
Indicates that one term is derived or obtained from another term, typically through a transformation, calculation, or logical inference.
-
D.
hasDerivativeUse
Indicates that one entity is used as a basis, source, or component for creating or enabling another entity or function.
-
E.
derivativeNamedAfter
Indicates that a derivative concept, result, or object is named in honor of a particular person or entity.
- 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_69f03199997c8190b6ae43fb19312443 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: April 28, 2026, 6:16 a.m.