Triple
T16436382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vandenberg |
E399188
|
entity |
| Predicate | hasReunion |
P122781
|
FINISHED |
| Object | Vandenberg 2020 lineup |
—
|
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: Vandenberg 2020 lineup | Statement: [Vandenberg, hasReunion, Vandenberg 2020 lineup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReunion Context triple: [Vandenberg, hasReunion, Vandenberg 2020 lineup]
-
A.
reunionOfAllMembers
Indicates that a gathering or event involves the complete set of members, with no one from the defined group absent.
-
B.
reunionType
Indicates the specific kind or category of reunion event that relates the involved entities.
-
C.
reunionEndYear
Indicates the calendar year in which a reunion event or recurring reunion relationship comes to an end.
-
D.
reunionContext
Indicates the situational setting, circumstances, or background in which a reunion between entities takes place.
-
E.
reunionYear
Indicates the year in which a reunion event takes place or is scheduled.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba224988190b7cccc42f35e54de |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.