Triple
T11169853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Tech Hokies women’s basketball |
E264244
|
entity |
| Predicate | recentStatus |
P28747
|
FINISHED |
| Object | nationally prominent program |
—
|
LITERAL 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: nationally prominent program | Statement: [Virginia Tech Hokies women’s basketball, recentStatus, nationally prominent program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recentStatus Context triple: [Virginia Tech Hokies women’s basketball, recentStatus, nationally prominent program]
-
A.
currentStatusSince
Indicates the point in time since which an entity has held its current status or state.
-
B.
modernStatus
chosen
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
-
C.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
D.
actualStatus
Indicates the current, real-world state or condition of an entity, as opposed to a planned, expected, or nominal status.
-
E.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8952e248190b0751669e8c960b7 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.