Triple
T37371246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilna |
E927848
|
entity |
| Predicate | referentHasCurrentOfficialName |
P20951
|
FINISHED |
| Object | Vilnius |
—
|
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: Vilnius | Statement: [Wilna, referentHasCurrentOfficialName, Vilnius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referentHasCurrentOfficialName Context triple: [Wilna, referentHasCurrentOfficialName, Vilnius]
-
A.
refersToOfficialName
Indicates that one entity is referencing or using the formally recognized, official name of another entity.
-
B.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
-
C.
modernNameOfficial
chosen
Indicates that an entity’s current, formally recognized name is the one specified.
-
D.
hasOfficialNameStatus
Indicates that an entity’s official name is associated with a particular status or classification (e.g., current, former, provisional).
-
E.
formerOfficialNameOf
Indicates that one entity was previously the official name of another entity before a renaming or reclassification.
- 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 3, 2026, 4:16 p.m.