Triple
T34790628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phi Delta Theta |
E1002933
|
entity |
| Predicate | originalChaptersAt |
P205558
|
FINISHED |
| Object | Miami University |
E124945
|
NE 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: Miami University | Statement: [Phi Delta Theta, originalChaptersAt, Miami University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalChaptersAt Context triple: [Phi Delta Theta, originalChaptersAt, Miami University]
-
A.
primarySourceChapters
Indicates that specific chapters are identified as the primary source material for the referenced content or work.
-
B.
beginsAtChapter
Indicates that an entity (such as a section, event, or reference) starts or first occurs at a specified chapter in a structured work.
-
C.
numberOfChapters
Indicates the total count of chapters associated with a given entity.
-
D.
containsChapter
Indicates that one entity (typically a larger work or document) includes another entity as a chapter within its structure.
-
E.
chapterOn
Indicates that one entity (typically a chapter) is about, discusses, or focuses on the subject represented by another entity.
- F. None of above. chosen
Provenance (5 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_69f76db47d408190a24fc7164439ea2d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a376fa3e0e08190be6c829fd8476215 |
completed | June 21, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 3:59 p.m.