Triple
T6828870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Report of the Office of the Secretary of Defense Vietnam Task Force |
E157085
|
entity |
| Predicate | startTimeOfEventsDescribed |
P288
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Report of the Office of the Secretary of Defense Vietnam Task Force, startTimeOfEventsDescribed, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfEventsDescribed Context triple: [Report of the Office of the Secretary of Defense Vietnam Task Force, startTimeOfEventsDescribed, 1945]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
eventOccurredAt
Indicates that a particular event took place at a specific time or location.
-
C.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
D.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
E.
allegedStartEvent
Indicates that an entity is claimed or reported (but not confirmed) to be the starting point or initiation of a particular event or process.
- 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_69c6882a5b5c8190917a7db9ed36bad1 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d6254bd88190a2a424537c2c12e2 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.