Triple
T177741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Sixteen |
E3611
|
entity |
| Predicate | levelInBracket |
P2393
|
FINISHED |
| Object | third weekend round |
—
|
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: third weekend round | Statement: [Sweet Sixteen, levelInBracket, third weekend round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelInBracket Context triple: [Sweet Sixteen, levelInBracket, third weekend round]
-
A.
meetsAtLevel
Indicates that two or more entities encounter or interact with each other at a specific hierarchical, structural, or progression level.
-
B.
hasLevel
chosen
Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
-
C.
trainingLevel
Indicates the degree or stage of training or skill development that an entity has attained.
-
D.
levelOnPyramid
Indicates the relative vertical tier or layer that an entity occupies within a pyramid structure.
-
E.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
- 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_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. |
Created at: Feb. 28, 2026, 2:39 a.m.