Triple
T33210510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messina |
E850142
|
entity |
| Predicate | centralActivityInWork |
P158255
|
FINISHED |
| Object | high school football |
—
|
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: high school football | Statement: [Messina, centralActivityInWork, high school football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralActivityInWork Context triple: [Messina, centralActivityInWork, high school football]
-
A.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
isCentralInWork
Indicates that an entity holds a primary, pivotal, or focal role within a given work (such as a text, artwork, or project).
-
D.
inWorkAct
chosen
Indicates that an entity participates in or is involved in a specific work-related action or activity.
-
E.
centralProject
Indicates that one project serves as the primary or core project around which other related projects or activities are organized.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 1, 2026, 1:30 a.m.