Triple
T23143409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Kings |
E577521
|
entity |
| Predicate | enteredPro14 |
P151083
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Southern Kings, enteredPro14, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredPro14 Context triple: [Southern Kings, enteredPro14, 2017]
-
A.
enteredInto
Indicates that one entity has initiated or become formally involved in a particular state, agreement, relationship, or situation with another entity.
-
B.
enteredIntoBy
Indicates that an agreement, contract, or formal arrangement has been initiated or established by a particular party.
-
C.
enteredServiceOnLine14
Indicates that an entity (such as a vehicle or piece of equipment) began operating in regular service on route or line 14.
-
D.
enteredSpace
Indicates that an entity has moved into or crossed the boundary into a particular space or area.
-
E.
entersBy
Indicates that one entity moves into or gains access to another entity through a specified entrance, route, or means.
- F. None of above. chosen
Provenance (4 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18ecc3710819088ac5d72dad0459a |
completed | April 29, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4 p.m.