Triple
T32614377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stan Lee Media |
E833744
|
entity |
| Predicate | claimedRightsTo |
P129049
|
FINISHED |
| Object | certain Marvel characters |
—
|
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: certain Marvel characters | Statement: [Stan Lee Media, claimedRightsTo, certain Marvel characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedRightsTo Context triple: [Stan Lee Media, claimedRightsTo, certain Marvel characters]
-
A.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
-
B.
claimedProperty
chosen
Indicates that one entity asserts ownership, possession, or a right over another entity or resource.
-
C.
claimsToBe
Indicates that one entity asserts or declares itself to have a particular identity, role, or property, regardless of whether this assertion is true.
-
D.
acquiredRightsTo
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
E.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:06 a.m.