Triple
T18598803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murray Island |
E454565
|
entity |
| Predicate | legalPrecedentFrom |
P132725
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Murray Island, legalPrecedentFrom, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalPrecedentFrom Context triple: [Murray Island, legalPrecedentFrom, 1992]
-
A.
legalPrecedentInvolved
Indicates that a particular legal precedent (prior court decision or ruling) is relevant to, cited in, or forms the basis for the current legal matter or action.
-
B.
usesLegalPrecedentFrom
Indicates that one legal case, decision, or argument relies on, cites, or is based upon the legal precedent established by another.
-
C.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
-
D.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
-
E.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
- F. None of above. chosen
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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474f1d548190b74408eabd396344 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.