Triple
T38070950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comics Code Authority |
E950586
|
entity |
| Predicate | lostMember |
P186126
|
FINISHED |
| Object | Marvel Comics |
—
|
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: Marvel Comics | Statement: [Comics Code Authority, lostMember, Marvel Comics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostMember Context triple: [Comics Code Authority, lostMember, Marvel Comics]
-
A.
lostFamilyMembersIn
Indicates that a person has family members who died or went missing as a result of a specified event, place, or time period.
-
B.
lostFrom
chosen
Indicates that an entity has been removed, misplaced, or no longer present from a specific source, location, or collection.
-
C.
lostCompanion
Indicates that one entity has lost another entity who had been accompanying or closely associated with them.
-
D.
lostTo
Indicates that one entity was defeated by another in a competition, conflict, or comparison.
-
E.
lostWith
Indicates that one entity experienced a loss or defeat in conjunction with, or as part of the same side/team as, another entity.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.