Triple
T25716386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Asylum Court |
E644873
|
entity |
| Predicate | decisionCanBeChallengedBefore |
P15175
|
FINISHED |
| Object | Conseil d’État |
E778702
|
NE 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: Conseil d’État | Statement: [National Asylum Court, decisionCanBeChallengedBefore, Conseil d’État]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionCanBeChallengedBefore Context triple: [National Asylum Court, decisionCanBeChallengedBefore, Conseil d’État]
-
A.
canBeChallengedOn
Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
-
B.
precedentChallenged
Indicates that an existing legal precedent is being questioned, disputed, or formally contested.
-
C.
decisionEnforceableIn
Indicates that a particular decision is legally valid and can be executed or enforced within a specified jurisdiction or context.
-
D.
stateChallenged
Indicates that a state or condition is being questioned, disputed, or formally contested by another party.
-
E.
mayBeChallengedBy
chosen
Indicates that one entity is allowed or able to be opposed, questioned, or contested by another entity.
- F. None of above.
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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10d9ff3df4819099b40aaf43cf83b6 |
completed | May 22, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 9:43 p.m.