Triple
T21249580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division III men’s soccer championship |
E523703
|
entity |
| Predicate | nonProfessional |
P143376
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NCAA Division III men’s soccer championship, nonProfessional, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonProfessional Context triple: [NCAA Division III men’s soccer championship, nonProfessional, true]
-
A.
professional
Indicates that one entity has a formal, occupation-related role, service, or expertise in relation to another entity.
-
B.
nonScholastic
Indicates that an activity, event, or attribute is related to areas outside formal academic or scholarly pursuits.
-
C.
professionalSince
Indicates the point in time when an entity began its professional activity or career in a given role or field.
-
D.
nonClerical
Indicates that an entity, role, or activity is not related to clerical or administrative work or duties.
-
E.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359c7a648190b4345336ac3be024 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:56 p.m.