Triple
T31315361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treacherous |
E798579
|
entity |
| Predicate | originallyAppearsOn |
P103992
|
FINISHED |
| Object | Red |
—
|
NE NERFINISHED |
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: Red | Statement: [Treacherous, originallyAppearsOn, Red]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyAppearsOn Context triple: [Treacherous, originallyAppearsOn, Red]
-
A.
originallyAppearedOn
chosen
Indicates the original source or platform where something (such as a work, content, or item) was first published, released, or made available.
-
B.
appearsInOriginalTitle
Indicates that an entity is mentioned or featured within the original (non-localized) title of another work or resource.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
E.
appearedAt
Indicates that an entity was present or made an appearance at a specific event, location, or occasion.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00ac5654a0819090701f61a5802d64 |
completed | May 10, 2026, 4:03 p.m. |
| PD | Predicate disambiguation | batch_6a00ab94b5e881909e15d1342e5f43be |
completed | May 10, 2026, 4 p.m. |
Created at: April 29, 2026, 9:15 p.m.