Triple
T7941843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Midnight Alarm |
E184409
|
entity |
| Predicate | hasRelativeNotability |
P58293
|
FINISHED |
| Object | lesser-known work of Grant Wood |
—
|
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: lesser-known work of Grant Wood | Statement: [The Midnight Alarm, hasRelativeNotability, lesser-known work of Grant Wood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativeNotability Context triple: [The Midnight Alarm, hasRelativeNotability, lesser-known work of Grant Wood]
-
A.
notableRelative
Indicates that an entity has a relative who is notable or well-known, specifying that familial relationship.
-
B.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as another entity.
-
C.
relativeNotability
chosen
Indicates how notable or prominent one entity is in comparison to another entity or set of entities.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
hasNotableReference
Indicates that one entity makes a significant or noteworthy mention of, or allusion to, another entity.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b0c16b8819093c5d1719cd65ee3 |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.