Triple
T3919119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WATSON |
E88914
|
entity |
| Predicate | operationalStart |
P3267
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [WATSON, operationalStart, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalStart Context triple: [WATSON, operationalStart, 2021]
-
A.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
B.
becameOperational
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.
-
C.
operationalCommand
Indicates that one entity issues or holds authoritative control over the actions or operations of another entity.
-
D.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
E.
fullyOperationalBy
Indicates that an entity is expected or required to be completely functional and ready for use no later than a specified time or event.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.