Triple
T37729304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemar Hoskins |
E940112
|
entity |
| Predicate | associatedWithMantle |
P100693
|
FINISHED |
| Object | Captain America legacy |
—
|
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: Captain America legacy | Statement: [Lemar Hoskins, associatedWithMantle, Captain America legacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMantle Context triple: [Lemar Hoskins, associatedWithMantle, Captain America legacy]
-
A.
isMantleUsedBy
chosen
Indicates that a mantle is utilized, worn, or otherwise employed by a particular entity.
-
B.
sharesMantleWith
Indicates that two entities occupy or are associated with the same mantle, layer, or mantle-like structure.
-
C.
isSecondToUseMantle
Indicates that one entity is the second individual or instance to assume or utilize a particular mantle, role, or title previously held by another.
-
D.
associatedWithMaterial
Indicates a relationship where something is linked or connected to a particular material, typically as its substance, component, or relevant physical medium.
-
E.
mantleType
Indicates the type or classification of a mantle associated with an entity, specifying what kind of mantle it has.
- 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.