Triple
T10123620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Instance Division |
E223356
|
entity |
| Predicate | levelOfAdjudication |
P71353
|
FINISHED |
| Object | first instance |
—
|
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: first instance | Statement: [First Instance Division, levelOfAdjudication, first instance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelOfAdjudication Context triple: [First Instance Division, levelOfAdjudication, first instance]
-
A.
canAdjudicate
Indicates that an entity has the authority or capacity to formally judge, decide, or resolve a dispute, case, or issue involving another entity or matter.
-
B.
levelOfAppeal
Indicates the degree or intensity to which something is attractive, interesting, or desirable to someone or something.
-
C.
hadCourtLevel
chosen
Indicates the specific hierarchical level of the court at which a legal case or judicial action took place.
-
D.
ordinationLevel
Indicates the hierarchical rank or degree of authority assigned to an entity within an ordered or structured system.
-
E.
assessmentLevel
Indicates the degree, rating, or intensity assigned to an evaluation or judgment of something.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd2ea7fe88190acb08d292a794638 |
completed | April 2, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba1d360819087698d04a53cc87e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:05 p.m.