Triple
T10059173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnson v. M’Intosh |
E208937
|
entity |
| Predicate | sourceOfTitleUpheld |
P91884
|
FINISHED |
| Object | federal land grants |
—
|
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: federal land grants | Statement: [Johnson v. M’Intosh, sourceOfTitleUpheld, federal land grants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceOfTitleUpheld Context triple: [Johnson v. M’Intosh, sourceOfTitleUpheld, federal land grants]
-
A.
defendedTitleAgainst
Indicates that one entity successfully retained a title or championship by competing against and overcoming a specific opponent.
-
B.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
-
C.
claimedTitle
Indicates that an entity asserts or declares possession of a particular title or rank.
-
D.
hasTitleInLaw
Indicates that an entity holds or is designated by a specific formal title as defined or recognized in law.
-
E.
titleSucceededFrom
Indicates that a person or entity obtained a title previously held by another, directly following them in succession.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcfb0f17c8190a8c0cfb02863537d |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b92573481909389bc6148ae7ea8 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:57 p.m.