Triple
T4142863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Sprat |
E89310
|
entity |
| Predicate | roleInRhyme |
P54122
|
FINISHED |
| Object | husband |
—
|
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: husband | Statement: [Jack Sprat, roleInRhyme, husband]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRhyme Context triple: [Jack Sprat, roleInRhyme, husband]
-
A.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
B.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
-
C.
genreRole
Indicates a relationship where an entity holds a specific functional or categorical role within a particular genre.
-
D.
musicalRole
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:43 p.m.