Triple
T21421856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conseil privé |
E528455
|
entity |
| Predicate | typeDeCompétence |
P132821
|
FINISHED |
| Object | compétence judiciaire suprême |
—
|
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: compétence judiciaire suprême | Statement: [Conseil privé, typeDeCompétence, compétence judiciaire suprême]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeDeCompétence Context triple: [Conseil privé, typeDeCompétence, compétence judiciaire suprême]
-
A.
skillType
chosen
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
B.
skillAssessed
Indicates that an entity’s skill or competency has been evaluated or measured, typically by another agent or process.
-
C.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
D.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
E.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
- 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_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. |
Created at: April 16, 2026, 5:48 p.m.