Triple
T18867164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inpw |
E461469
|
entity |
| Predicate | hasNameVariant |
P457
|
FINISHED |
| Object | Inpu |
—
|
NE NERFINISHED |
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: Inpu | Statement: [Inpw, hasNameVariant, Inpu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Inpu Context triple: [Inpw, hasNameVariant, Inpu]
-
A.
Iput
Iput is a river in Eastern Europe that flows through parts of Russia and Belarus before joining the Sozh River.
-
B.
Iputinga
Iputinga is a neighborhood located in the city of Recife, in the state of Pernambuco, Brazil.
-
C.
Iput I
chosen
Iput I was an ancient Egyptian queen of the Sixth Dynasty, likely a consort of King Teti and mother of King Pepi I Meryre.
-
D.
Iuput I
Iuput I was an early pharaoh of Egypt’s Twenty-third Dynasty, ruling from Leontopolis during the politically fragmented Third Intermediate Period.
-
E.
Iuput A
Iuput A was an ancient Egyptian prince and high priest of Amun during the early 22nd Dynasty, active in the reign of his father, Pharaoh Shoshenq I.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dcfb7b9c8190854e7b171b98ea2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c2a617548190be6044bf2c3de6d0 |
completed | April 20, 2026, 6:07 a.m. |
Created at: April 10, 2026, 11:57 a.m.