Triple
T17148079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NET |
E416145
|
entity |
| Predicate | initialVersionIncluded |
P83108
|
FINISHED |
| Object | team value index (TVI) |
—
|
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: team value index (TVI) | Statement: [NET, initialVersionIncluded, team value index (TVI)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialVersionIncluded Context triple: [NET, initialVersionIncluded, team value index (TVI)]
-
A.
previousVersionIncluded
Indicates that an earlier version of an entity was contained within, or formed part of, the current entity.
-
B.
officialVersionIncludes
Indicates that an official or authoritative version of something contains, incorporates, or encompasses a specified component, element, or subset.
-
C.
principalVersionFor
Indicates a relationship where one version of an entity is designated as the primary or authoritative version for another related entity.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
earlyVersion
chosen
Indicates that one entity is an earlier or preliminary version of another entity in a version sequence.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f404f0e88190b7ac9ac523fdc7da |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.