Triple
T29051173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Comics adaptations |
E735264
|
entity |
| Predicate | notableCharacterAdapted |
P112632
|
FINISHED |
| Object | Spider-Man |
E123778
|
NE 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: Spider-Man | Statement: [Marvel Comics adaptations, notableCharacterAdapted, Spider-Man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterAdapted Context triple: [Marvel Comics adaptations, notableCharacterAdapted, Spider-Man]
-
A.
notableForAdaptationsOf
Indicates that one entity is recognized or distinguished for creating, producing, or being associated with adaptations of another entity.
-
B.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
C.
notableAdaptationElement
chosen
Indicates that one work is a significant adaptation or reinterpretation of another work.
-
D.
notableCharacterName
Indicates that the subject has a notable or significant character whose name is given by the object.
-
E.
notableSeriesCharacter
Indicates that an entity is a significant or well-known character appearing in a particular series.
- F. None of above.
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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0212b3462c8190ba3587852cb10655 |
completed | May 11, 2026, 5:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f695ca481908026b9ea02c85ca7 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a020f3138a48190ac630e810939e881 |
completed | May 11, 2026, 5:17 p.m. |
Created at: April 28, 2026, 10:08 a.m.