Triple
T25475088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grail |
E638409
|
entity |
| Predicate | systemEnteredService |
P2339
|
FINISHED |
| Object | 1960s |
—
|
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: 1960s | Statement: [Grail, systemEnteredService, 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemEnteredService Context triple: [Grail, systemEnteredService, 1960s]
-
A.
enteredService
chosen
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
-
C.
enteredServiceBefore
Indicates that one entity began its period of service earlier in time than another entity.
-
D.
enteredIntoApplication
Indicates that one entity has been provided or recorded as input within an application or application process.
-
E.
serviceSystem
Indicates a relationship where one entity functions as a service system that provides, manages, or supports services for another entity.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f754447c8190acc16c440f8bb03d |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 2:25 p.m.