Triple
T21421866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil privé |
E528455
|
entity |
| Predicate | composéDe |
P143902
|
FINISHED |
| Object | conseillers d’État |
—
|
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: conseillers d’État | Statement: [Conseil privé, composéDe, conseillers d’État]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composéDe Context triple: [Conseil privé, composéDe, conseillers d’État]
-
A.
composedIn
Indicates that a creative work was written or musically composed within a particular place or during a specific time period.
-
B.
composedTo
Indicates that one entity created or authored another entity, typically a work such as a piece of music, writing, or art.
-
C.
partOfComposition
Indicates that one entity is a component, section, or constituent element within a larger composite whole represented by another entity.
-
D.
isComposedIn
Indicates that something is created, written, or formed within a particular context, medium, or framework.
-
E.
composedFor
Indicates that a creative work (typically a piece of music) was specifically written or created for a particular person, group, event, or purpose.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2d17f5081908f0185011eae3160 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 5:48 p.m.