Triple
T23244870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC 349 |
E581558
|
entity |
| Predicate | appearanceInImages |
P151521
|
FINISHED |
| Object | small intensely bright patch near Merope |
—
|
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: small intensely bright patch near Merope | Statement: [IC 349, appearanceInImages, small intensely bright patch near Merope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearanceInImages Context triple: [IC 349, appearanceInImages, small intensely bright patch near Merope]
-
A.
hasCharacterAppearance
Indicates that a character appears or is visually represented within a given work, scene, or context.
-
B.
appearsWithCharacter
Indicates that two characters are shown or present together within the same scene, shot, or context.
-
C.
wasPhotographedAs
Indicates that one entity appears in a photograph specifically portraying them in the role, character, or identity of another entity.
-
D.
appearedWith
Indicates that two entities were present or participated together in the same context, event, or medium.
-
E.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:10 p.m.