Triple
T10722356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvera |
E252853
|
entity |
| Predicate | enemyOf |
P437
|
FINISHED |
| Object | Vin |
E99211
|
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: Vin | Statement: [Calvera, enemyOf, Vin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vin Context triple: [Calvera, enemyOf, Vin]
-
A.
Vin
chosen
Vin is a common shortened form of the given name Vincent, often used as an informal or familiar nickname.
-
B.
Ven
Ven is a small Swedish island in the Øresund Strait, known for its scenic landscapes, cycling paths, and historical association with astronomer Tycho Brahe.
-
C.
VIC
VIC is the National Rail station code for London Victoria, a major central London railway terminus and Underground station.
-
D.
VIC
VIC is the standard abbreviation for the Australian state of Victoria, commonly used in postal addresses and official contexts.
-
E.
Vi
Vi is the codename of Vi Moradi, a Resistance spy and intelligence operative in the Star Wars universe known for her missions against the First Order.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d44d0048190a78aae2357e864a5 |
completed | April 9, 2026, 2:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dbb738f8488190837a675b82ce75aa |
completed | April 12, 2026, 3:16 p.m. |
Created at: April 8, 2026, 9:13 p.m.