Triple
T25716378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Asylum Court |
E644873
|
entity |
| Predicate | partyInProceedings |
P159007
|
FINISHED |
| Object | OFPRA |
—
|
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: OFPRA | Statement: [National Asylum Court, partyInProceedings, OFPRA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyInProceedings Context triple: [National Asylum Court, partyInProceedings, OFPRA]
-
A.
partyInProceedings
chosen
Indicates that an entity participates as a party in a specific legal or administrative proceeding.
-
B.
proceedingsAre
Indicates that certain events, actions, or legal steps constitute or are recognized as formal proceedings.
-
C.
publishesProceedingsFor
Indicates that an entity (such as a publisher or organization) produces and makes publicly available the official proceedings for a particular event, conference, or meeting.
-
D.
parallelConference
Indicates that two or more conferences occur at the same time or overlap in schedule, running in parallel to each other.
-
E.
partOfConference
Indicates that an entity is included as a component or segment within a specific conference.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc6211788190bb46c645902c2bc2 |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 9:43 p.m.