Triple
T31283493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | parquets généraux près les cours d’appel |
E797737
|
entity |
| Predicate | agitDevant |
P143900
|
FINISHED |
| Object | cours d’appel françaises |
—
|
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: cours d’appel françaises | Statement: [parquets généraux près les cours d’appel, agitDevant, cours d’appel françaises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agitDevant Context triple: [parquets généraux près les cours d’appel, agitDevant, cours d’appel françaises]
-
A.
seDérouleAutourDe
Indicates that an event or process takes place around, centers on, or is organized about a particular entity or theme.
-
B.
relèveDe
chosen
Indicates that one entity is under the authority, responsibility, or jurisdiction of another entity.
-
C.
neDoitPasÊtreConfonduAvec
Indicates that one entity should not be mistaken for, or confused with, another distinct entity.
-
D.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
E.
frontIn
Indicates that one entity is positioned directly in front of another entity in space or sequence.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:13 p.m.