Triple
T26429201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maria Rambeau |
E664453
|
entity |
| Predicate | inspiredCallsignOf |
P164839
|
FINISHED |
| Object | Monica Rambeau |
—
|
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: Monica Rambeau | Statement: [Maria Rambeau, inspiredCallsignOf, Monica Rambeau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredCallsignOf Context triple: [Maria Rambeau, inspiredCallsignOf, Monica Rambeau]
-
A.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
-
B.
callsignSeries
Indicates that one entity is a member or installment within a series or sequence that shares the same callsign.
-
C.
callsignSupported
Indicates that a system or service is capable of recognizing, handling, or using a particular callsign.
-
D.
formerCallSign
Indicates that one identifier was previously used as the call sign for the other entity before being changed or replaced.
-
E.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
- 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_69f650fc44e48190bc0e0a935eac62a6 |
completed | May 2, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f650c466b881908954e43bfebae8a4 |
completed | May 2, 2026, 7:30 p.m. |
Created at: April 26, 2026, 11:47 p.m.