Triple
T11821927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference National |
E281159
|
entity |
| Predicate | currentNameSince |
P21184
|
FINISHED |
| Object | 2015–16 season |
—
|
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: 2015–16 season | Statement: [Conference National, currentNameSince, 2015–16 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentNameSince Context triple: [Conference National, currentNameSince, 2015–16 season]
-
A.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
B.
currentNameUsedFrom
chosen
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
-
C.
nameUsedSince
Indicates that a particular name has been in use for an entity starting from a specified point in time.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.