Triple
T16853992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VPAID |
E409740
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | VAST |
E84600
|
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: VAST | Statement: [VPAID, relatedTo, VAST]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VAST Context triple: [VPAID, relatedTo, VAST]
-
A.
VAST
chosen
VAST (Video Ad Serving Template) is an industry-standard XML-based specification that defines how video ads are served and tracked across different video players and ad servers.
-
B.
VAB
VAB is the commonly used abbreviation for NASA’s Vehicle Assembly Building, the massive structure at Kennedy Space Center where rockets are assembled before launch.
-
C.
VASS
VASS is Vietnam’s leading national research institution dedicated to the study and development of the social sciences.
-
D.
VAND
VAND is the ICAO airport code assigned to Shri Guru Gobind Singh Ji Airport in India.
-
E.
VAN
VAN is the standard abbreviation used for the Vancouver Canadians, a Minor League Baseball team based in Vancouver, British Columbia.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37bbb80819086d844a313625cad |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2a6f2c48190874839f78f943fdb |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:24 a.m.