Triple
T12300725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John O. Rankin |
E293212
|
entity |
| Predicate | hasNotableWorkOn |
P21402
|
FINISHED |
| Object | Unami syntax |
E75801
|
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: Unami syntax | Statement: [John O. Rankin, hasNotableWorkOn, Unami syntax]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unami syntax Context triple: [John O. Rankin, hasNotableWorkOn, Unami syntax]
-
A.
Unami
chosen
Unami is a dialect of the Lenape (Delaware) language historically spoken by the Lenape people in parts of the mid-Atlantic region of North America.
-
B.
UNAMI
UNAMI is a United Nations political mission established to support Iraq’s political transition, reconciliation, and reconstruction efforts.
-
C.
UMI
UMI is the three-letter ISO 3166-1 alpha-3 country code assigned to Kingman Reef, an uninhabited U.S. territory in the central Pacific Ocean.
-
D.
UNOMIG
UNOMIG was a United Nations peacekeeping mission established to monitor the ceasefire and support conflict resolution efforts in the Georgian–Abkhaz conflict.
-
E.
UMAC
UMAC is a high-speed, universal hash-based message authentication code designed for efficient and secure data integrity verification in modern cryptographic systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93edb59908190bcef9d0cdc11081f |
completed | April 10, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e7d757881908ac6af2b70a6dafe |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:53 p.m.