Triple
T10511896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Conference basketball teams (visiting) |
E247934
|
entity |
| Predicate | mayFace |
P94307
|
FINISHED |
| Object | other SEC basketball teams |
—
|
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: other SEC basketball teams | Statement: [Southeastern Conference basketball teams (visiting), mayFace, other SEC basketball teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayFace Context triple: [Southeastern Conference basketball teams (visiting), mayFace, other SEC basketball teams]
-
A.
mustFace
Indicates that one entity is required or obligated to orient or direct its front side toward another entity or reference point.
-
B.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
-
C.
mayMask
Indicates that one entity is permitted or able to conceal, obscure, or hide another entity or its properties.
-
D.
hasFace
Indicates that one entity possesses, displays, or is characterized by a face.
-
E.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509b5fcb8819087a23a2b26aecd70 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:27 p.m.