Triple
T35007940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rachel Roth |
E1009862
|
entity |
| Predicate | civilianIdentityOf |
P165853
|
FINISHED |
| Object | Raven |
—
|
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: Raven | Statement: [Rachel Roth, civilianIdentityOf, Raven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilianIdentityOf Context triple: [Rachel Roth, civilianIdentityOf, Raven]
-
A.
hasCivilianIdentity
chosen
Indicates that an entity possesses a non-superhero, everyday personal identity used in civilian life.
-
B.
hasCivilianIdentityIntroduced
Indicates that an entity’s civilian (non-superpowered or non-professional) identity has been revealed or established within the context of the narrative or dataset.
-
C.
hasCivicIdentity
Indicates that an entity possesses a recognized status, role, or affiliation within a civic, social, or political community.
-
D.
civilianEligibility
Indicates that an entity meets the criteria or conditions required to be classified or treated as a civilian in a given context.
-
E.
isCivilian
Indicates that an entity is a non-military, non-combatant individual in the context of a given situation or system.
- 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_69f76dcb716881909f75e4fd60ab2284 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.