Triple
T33393415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Wayne as Rooster Cogburn |
E855109
|
entity |
| Predicate | notableVisualFeature |
P200117
|
FINISHED |
| Object | battered hat |
—
|
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: battered hat | Statement: [John Wayne as Rooster Cogburn, notableVisualFeature, battered hat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVisualFeature Context triple: [John Wayne as Rooster Cogburn, notableVisualFeature, battered hat]
-
A.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
B.
notableAppearanceFeature
chosen
Indicates that an entity is characterized by a distinctive or noteworthy physical appearance trait.
-
C.
notableLocationFeature
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
D.
hasParticularNotableCharacteristic
Indicates that an entity possesses a specific, noteworthy characteristic or quality that distinguishes it in some relevant context.
-
E.
iconicFeature
Indicates that something serves as a distinctive, widely recognized characteristic or symbol of 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:35 a.m.