Triple
T15473317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ten wrestling |
E376718
|
entity |
| Predicate | hasIndividualTitle |
P28484
|
FINISHED |
| Object | conference individual championship |
—
|
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: conference individual championship | Statement: [Big Ten wrestling, hasIndividualTitle, conference individual championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndividualTitle Context triple: [Big Ten wrestling, hasIndividualTitle, conference individual championship]
-
A.
isIndividualTitle
chosen
Indicates that a given title refers to a single, specific individual rather than a group, organization, or collective entity.
-
B.
hasAuthorTitle
Indicates that an author holds or is designated by a specific title (e.g., professional, honorific, or role-based).
-
C.
hasTitleWork
Indicates that an entity is associated with a specific work by its title (i.e., the entity has or bears that work’s title).
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hadTitle
Indicates that an entity held or was assigned a specific title or formal designation.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.