Triple
T28038262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolverine |
E708470
|
entity |
| Predicate | fullFirstAppearance |
P29367
|
FINISHED |
| Object | The Incredible Hulk #181 |
—
|
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: The Incredible Hulk #181 | Statement: [Wolverine, fullFirstAppearance, The Incredible Hulk #181]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullFirstAppearance Context triple: [Wolverine, fullFirstAppearance, The Incredible Hulk #181]
-
A.
airDateOfFirstAppearance
Indicates the calendar date on which an entity (such as a character, show, or episode) was first broadcast or made publicly available.
-
B.
firstAppearanceFor
chosen
Indicates that an entity marks the initial occurrence or debut of another entity within a given context or medium.
-
C.
settingOfFirstAppearance
Indicates the location or context in which an entity is first introduced or appears.
-
D.
firstAppearancePublisher
Indicates the publisher responsible for releasing an entity’s first appearance.
-
E.
firstAppearanceApprox
Indicates that one entity is the approximate or estimated first appearance of another entity in time or context.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63f2e1a248190a41f02f91e8c1183 |
completed | May 2, 2026, 6:15 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:23 p.m.