Triple
T8284778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | z/VSE |
E193762
|
entity |
| Predicate | family |
P566
|
FINISHED |
| Object | VSE |
E482738
|
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: VSE | Statement: [z/VSE, family, VSE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VSE Context triple: [z/VSE, family, VSE]
-
A.
VŠE
chosen
VŠE is the commonly used abbreviation for the University of Economics in Prague, a leading Czech institution specializing in economics and business studies.
-
B.
VES
VES is an abbreviation for the Virtual Execution System, a runtime environment designed to execute managed code in a platform-independent manner.
-
C.
VSI
VSI is the commonly used abbreviation for the "Very Short Introductions" series of concise, authoritative books published by Oxford University Press on a wide range of subjects.
-
D.
VS
VS is the two-letter abbreviation commonly used for the Swiss canton of Valais.
-
E.
Ves'
Ves' was a medieval Slavic tribe or polity traditionally associated with the early formation of the Kievan Rus' state.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7ad20ae481908179aba245c73fad |
completed | March 31, 2026, 7:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd687e64a08190a45a1cf5f5c32291 |
completed | April 1, 2026, 6:48 p.m. |
Created at: March 30, 2026, 5:52 p.m.