Triple
T557335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section VIII |
E11970
|
entity |
| Predicate | Division 1Focus |
P16361
|
FINISHED |
| Object | pressure vessels using design-by-rule |
—
|
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: pressure vessels using design-by-rule | Statement: [Section VIII, Division 1Focus, pressure vessels using design-by-rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Division 1Focus Context triple: [Section VIII, Division 1Focus, pressure vessels using design-by-rule]
-
A.
competesInDivision
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
teamDivisionControlled
Indicates that one entity has authority over or manages the organizational structure or division of a team.
-
D.
NCAADivision
Indicates the competitive division within the NCAA in which an institution or team participates.
-
E.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a499dd84ec81909d2b309da057b9c6 |
completed | March 1, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.