Triple
T6688708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobian language |
E152167
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Tobi |
E543518
|
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: Tobi | Statement: [Tobian language, hasAlternativeName, Tobi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tobi Context triple: [Tobian language, hasAlternativeName, Tobi]
-
A.
Tobi
chosen
Tobi is a given name, often used as a variant of Toby, that can be used for people of any gender in various cultures.
-
B.
Tio
Tio is a coastal town in Eritrea’s Southern Red Sea Region, known historically as a small port on the Red Sea.
-
C.
Nagato
Nagato was a famous Japanese battleship of the Imperial Japanese Navy, notable for serving as Admiral Yamamoto’s flagship during the attack on Pearl Harbor and later participating in major World War II engagements.
-
D.
Tobie
Tobie is a given name, typically used as a variant spelling of Toby.
-
E.
Obi
Obi is a local government area in Nasarawa State, Nigeria, serving as an administrative subdivision of the state.
- 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_69c687f9977c819097e7f5ada4fe522e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b14feb28819097bc157df8a2f96e |
completed | March 27, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c6f7b31fa0819089c4debbbbce9d22 |
completed | March 27, 2026, 9:33 p.m. |
Created at: March 27, 2026, 2:04 p.m.