Triple
T26429179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Rambeau |
E664453
|
entity |
| Predicate | callsByNickname |
P160747
|
FINISHED |
| Object | Carol Danvers |
—
|
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: Carol Danvers | Statement: [Maria Rambeau, callsByNickname, Carol Danvers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callsByNickname Context triple: [Maria Rambeau, callsByNickname, Carol Danvers]
-
A.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
-
B.
famousCall
Indicates that one entity makes a phone call to another entity who is widely known or celebrated.
-
C.
famousCallBy
Indicates that one entity is famously referred to or called by a particular name or title by another entity or source.
-
D.
displayCall
Indicates that one entity presents or shows a call (such as a phone call or function call) to another entity or to a user interface.
-
E.
hasCallInNumber
Indicates that an entity has an associated telephone number designated for receiving incoming calls.
- F. None of above. chosen
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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611bc79f48190ad06b5264817251d |
completed | May 2, 2026, 3:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 26, 2026, 11:47 p.m.