Triple
T38370684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I. The Worst Guys |
E892568
|
entity |
| Predicate | hasTitleSectionPrefix |
P197404
|
FINISHED |
| Object | I. |
—
|
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: I. | Statement: [I. The Worst Guys, hasTitleSectionPrefix, I.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleSectionPrefix Context triple: [I. The Worst Guys, hasTitleSectionPrefix, I.]
-
A.
hasTitleSetting
Indicates that an entity is associated with a specific title that defines or describes its setting.
-
B.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
C.
hasTitleBranch
Indicates that an entity holds or is associated with a specific title within a particular branch, division, or subdivision of an organization or structure.
-
D.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
-
E.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: May 3, 2026, 4:31 p.m.