Triple
T27543888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Challenge League |
E695307
|
entity |
| Predicate | inceptionStatus |
P61
|
FINISHED |
| Object | planned |
—
|
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: planned | Statement: [AFC Challenge League, inceptionStatus, planned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inceptionStatus Context triple: [AFC Challenge League, inceptionStatus, planned]
-
A.
inceptionWithin
Indicates that one event, process, or entity begins or is initiated entirely within the temporal or spatial bounds of another.
-
B.
inception
chosen
Indicates the point in time or event at which something begins, originates, or is first established.
-
C.
inceptionBefore
Indicates that one entity’s beginning, creation, or initiation occurs earlier in time than that of another entity.
-
D.
inceptionPart
Indicates that one entity represents a component, segment, or phase within the initial creation or starting process of another entity.
-
E.
inceptionSeason
Indicates the season in which something (such as a series, competition, or activity) first began or was introduced.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f83176c81909a508c03229dc69d |
completed | May 2, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:32 p.m.