Triple
T177783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elite Eight |
E3612
|
entity |
| Predicate | isColloquialTerm |
P6990
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Elite Eight, isColloquialTerm, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isColloquialTerm Context triple: [Elite Eight, isColloquialTerm, yes]
-
A.
regionalDialect
Indicates that one entity uses or is associated with a dialect specific to a particular geographic region in relation to another entity.
-
B.
isWidelySpokenIn
Indicates that a language is spoken by a large portion of the population across many regions or communities within a specified area.
-
C.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
-
D.
hasExonym
Indicates that one entity is known by an alternative name or designation in another language or cultural context.
-
E.
recognizedRegionalLanguage
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fe7bb08190a56f4a54cadd2fef |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.