Triple
T33773203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navin |
E865440
|
entity |
| Predicate | commonSpellingInDiaspora |
P29689
|
FINISHED |
| Object | Navin |
—
|
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: Navin | Statement: [Navin, commonSpellingInDiaspora, Navin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSpellingInDiaspora Context triple: [Navin, commonSpellingInDiaspora, Navin]
-
A.
sharesSpellingWith
chosen
Indicates that two entities have identical or substantially identical written forms (i.e., they are spelled the same way).
-
B.
spokenInDiaspora
Indicates that a language or dialect is used by a community living outside its original homeland or region of origin.
-
C.
currentOfficialSpelling
Indicates the officially recognized and currently valid spelling form of a given name or term.
-
D.
diasporaTerm
Indicates that a term specifically refers to, describes, or is used within the context of a diaspora community or diasporic experience.
-
E.
equivalentInDiaspora
Indicates that two entities are considered equivalent or correspond to each other within a diaspora context, such as representing the same role, function, or identity across different diaspora communities.
- F. None of above.
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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 1, 2026, 1:45 a.m.