Triple
T2893237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Vian |
E63875
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Vian |
E63875
|
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: Vian | Statement: [Philip Vian, familyName, Vian]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vian Context triple: [Philip Vian, familyName, Vian]
-
A.
Vian
chosen
Vian is a surname most notably associated with British Royal Navy Admiral Philip Vian, who served with distinction during both World Wars.
-
B.
Verny
Verny was the historical name of the city now known as Almaty, a major cultural and economic center in Kazakhstan.
-
C.
Corine
Corine is a feminine given name used in various European countries, often considered a variant of "Corinne."
-
D.
Visé
Visé is a municipality in eastern Belgium situated along the Meuse River in the province of Liège, known for its historic town center and strategic location near the Dutch border.
-
E.
Valleiry
Valleiry is a small French commune in the Haute-Savoie department of the Auvergne-Rhône-Alpes region in southeastern France, near the Swiss border.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe062234c81909411e34db7d2683d |
completed | March 7, 2026, 8:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b031814764819096a1664b468ec817 |
completed | March 10, 2026, 2:58 p.m. |
Created at: March 6, 2026, 10:07 p.m.