Triple
T34771665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme |
E1002377
|
entity |
| Predicate | enteredRegularServiceOn |
P148888
|
FINISHED |
| Object | 1 July 2020 |
—
|
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: 1 July 2020 | Statement: [Supreme, enteredRegularServiceOn, 1 July 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredRegularServiceOn Context triple: [Supreme, enteredRegularServiceOn, 1 July 2020]
-
A.
enteredServiceOn
chosen
Indicates the date or time when an entity first began active use, operation, or service.
-
B.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
C.
enteredServiceOnRoute
Indicates that an entity (typically a vehicle or service) began operating on a specific route starting from a particular date or time.
-
D.
enteredServiceBefore
Indicates that one entity began its period of service earlier in time than another entity.
-
E.
enteredServiceRole
Indicates that an entity has begun serving in a particular role, position, or capacity.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 3:59 p.m.