Triple
T27528779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VERITAS |
E694910
|
entity |
| Predicate | beganFullOperations |
P21563
|
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: [VERITAS, beganFullOperations, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganFullOperations Context triple: [VERITAS, beganFullOperations, 2007]
-
A.
trialOperationsBegan
Indicates that the operational phase of a trial has started.
-
B.
underlyingCommencedOperations
Indicates that the referenced underlying entity has begun its operational activities or business functions.
-
C.
beganCivilOperations
Indicates that an entity initiated or commenced civil (non-military) administrative or operational activities in relation to another entity or context.
-
D.
operationStart
Indicates the point in time or event at which a specific operation or process begins.
-
E.
becameOperational
chosen
Indicates that an entity transitioned from a non-functioning or inactive state to an active, functioning, or service-ready state at a certain 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f31e12c8190880b758fef6a07e0 |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:25 p.m.