Triple
T19762631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ceará Sporting Club |
E474667
|
entity |
| Predicate | hasRegionalTitle |
P14832
|
FINISHED |
| Object | Copa do Nordeste titles |
—
|
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: Copa do Nordeste titles | Statement: [Ceará Sporting Club, hasRegionalTitle, Copa do Nordeste titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalTitle Context triple: [Ceará Sporting Club, hasRegionalTitle, Copa do Nordeste titles]
-
A.
regionalTitles
chosen
Indicates that an entity holds or is associated with titles or designations that are specific to particular geographic regions.
-
B.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
C.
hasAlternateTitleRegion
Indicates that an entity has an alternate title that is specifically used or valid within a particular geographic region.
-
D.
subRegionalTitles
Indicates that an entity has one or more titles that apply specifically within a sub-region of a larger region or jurisdiction.
-
E.
hasLatinTitle
Indicates that an entity possesses a title or name expressed in Latin.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65320df3c8190b34f9908d5da48d9 |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.