Triple
T18016105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOCSegmentation |
E431001
|
entity |
| Predicate | supportsYear |
P130123
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [VOCSegmentation, supportsYear, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsYear Context triple: [VOCSegmentation, supportsYear, 2007]
-
A.
includesYear
Indicates that one entity contains, references, or is associated with a specific calendar year as part of its information or scope.
-
B.
deprecatedYear
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
-
C.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
D.
endorsedInYear
Indicates that one entity formally expressed support or approval for another entity during a specified calendar year.
-
E.
returnYear
Indicates the year in which something is returned or given back to its original owner, place, or state.
- F. None of above. chosen
Provenance (4 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.