Triple
T22338002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taça da Liga |
E552200
|
entity |
| Predicate | finalUsuallyHeldIn |
P147837
|
FINISHED |
| Object | January |
—
|
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: January | Statement: [Taça da Liga, finalUsuallyHeldIn, January]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalUsuallyHeldIn Context triple: [Taça da Liga, finalUsuallyHeldIn, January]
-
A.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
B.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
-
C.
finalUsuallyOn
Indicates that an event or process typically concludes or reaches its final state on a particular time, date, or condition.
-
D.
areHeldIn
Indicates that events, activities, or objects take place or are located within a particular venue, container, or setting.
-
E.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1578184f481908d4ec1737a8a72d4 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.