Triple
T12801445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phi Delta Theta |
E306027
|
entity |
| Predicate | hasChapterType |
P20981
|
FINISHED |
| Object | collegiate chapter |
—
|
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: collegiate chapter | Statement: [Phi Delta Theta, hasChapterType, collegiate chapter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChapterType Context triple: [Phi Delta Theta, hasChapterType, collegiate chapter]
-
A.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
B.
hasGeneralChapter
Indicates that an entity is associated with, or contains, a general chapter (a broad or overarching section) within a larger structured document or framework.
-
C.
chapterType
chosen
Indicates the specific kind or category of a chapter within a larger work or document.
-
D.
hasLocalChaptersIn
Indicates that an organization maintains one or more local chapters or branches within a specified geographic area or location.
-
E.
hadChapterOf
Indicates that an entity (such as a book or document) includes or contains a specific chapter as one of its parts.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7d3f5c8190bf01bef5d263ca26 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.