Triple
T36797272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jones v. United States |
E909216
|
entity |
| Predicate | locationSubject |
P47308
|
FINISHED |
| Object | Navassa Island |
E264039
|
NE 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: Navassa Island | Statement: [Jones v. United States, locationSubject, Navassa Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationSubject Context triple: [Jones v. United States, locationSubject, Navassa Island]
-
A.
subjectLocation
chosen
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
B.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
C.
locationFocus
Indicates that the primary or most relevant location associated with an entity, event, or relation is being specified or emphasized.
-
D.
subjectLocationType
Indicates the type or category of location associated with the subject in the relationship.
-
E.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
- F. None of above.
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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a0e5a481908b4115508ec91485 |
completed | June 29, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.