Triple
T9408062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passamaquoddy |
E226634
|
entity |
| Predicate | notableLegalIssue |
P4511
|
FINISHED |
| Object | land claims in Maine |
—
|
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: land claims in Maine | Statement: [Passamaquoddy, notableLegalIssue, land claims in Maine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLegalIssue Context triple: [Passamaquoddy, notableLegalIssue, land claims in Maine]
-
A.
notableAreaOfLaw
Indicates that a person or entity is particularly recognized or distinguished in a specific field or area of law.
-
B.
notableLegalWork
Indicates that an entity is recognized for significant contributions, cases, or achievements within the field of law.
-
C.
notableLegalCode
Indicates that a legal code is especially significant, influential, or noteworthy in relation to the referenced entity.
-
D.
hasLegalIssue
chosen
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
E.
notableSupremeCourtCase
Indicates that a legal case is recognized as a significant or influential decision by the Supreme Court.
- 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_69ca843280488190bc65600e843ef9e6 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5252b3fc8190b0808a10987728c8 |
completed | April 1, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69cca54c37f88190bddccf28e5fe5c84 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:47 p.m.