Triple
T29228617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luphomoid (MCU) |
E741001
|
entity |
| Predicate | firstKnownMemberOnScreen |
P121961
|
FINISHED |
| Object | Nebula (MCU) |
—
|
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: Nebula (MCU) | Statement: [Luphomoid (MCU), firstKnownMemberOnScreen, Nebula (MCU)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstKnownMemberOnScreen Context triple: [Luphomoid (MCU), firstKnownMemberOnScreen, Nebula (MCU)]
-
A.
lastKnownMember
Indicates that the subject is the most recent or final identified member of a particular group, lineage, or set.
-
B.
hasOnScreenRelative
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
-
C.
firstOnPageAppearance
Indicates the position where an entity appears for the first time on a given page.
-
D.
firstMember
chosen
Indicates that one entity is the first member or element in an ordered collection or group relative to the others.
-
E.
firstScreenedAs
Indicates that an entity was initially shown, presented, or tested in a particular screening context or medium.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.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 28, 2026, 12:17 p.m.