Triple
T31495590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Dawson Calvert |
E803530
|
entity |
| Predicate | keepsSecretIdentityFrom |
P66535
|
FINISHED |
| Object | Brock Lovett’s team |
—
|
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: Brock Lovett’s team | Statement: [Rose Dawson Calvert, keepsSecretIdentityFrom, Brock Lovett’s team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keepsSecretIdentityFrom Context triple: [Rose Dawson Calvert, keepsSecretIdentityFrom, Brock Lovett’s team]
-
A.
hasSecretIdentity
Indicates that an entity possesses an alternate, hidden identity that is not publicly known.
-
B.
usesSuperheroIdentity
Indicates that an entity adopts or operates under a superhero persona or alias, rather than their ordinary identity.
-
C.
knowsSecretIdentityOf
chosen
Indicates that one entity is aware of the hidden or private true identity of another entity.
-
D.
hasSuperheroIdentityType
Indicates the type or category of a superhero identity associated with an entity (e.g., secret, public, dual).
-
E.
keepsSecretAbout
Indicates that one entity intentionally withholds or conceals information regarding another specified entity or topic from others.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e8f46c819085d3019e45989d9c |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:41 p.m.