Triple
T3132018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Bolton |
E65435
|
entity |
| Predicate | serviceStartTime |
P288
|
FINISHED |
| Object | 1970 (Maryland Army National Guard) |
—
|
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: 1970 (Maryland Army National Guard) | Statement: [John Bolton, serviceStartTime, 1970 (Maryland Army National Guard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStartTime Context triple: [John Bolton, serviceStartTime, 1970 (Maryland Army National Guard)]
-
A.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
B.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
C.
serviceDuring
Indicates that one entity performs or provides a service for another entity during a specified time period or event.
-
D.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
E.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
- 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_69ad8581c25c8190b0d85ba9b9baa531 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada55f77b881908866fc43bdb18185 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.