Triple
T29082952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadliest Woman in the Galaxy |
E734025
|
entity |
| Predicate | scopeOfEpithet |
P104657
|
FINISHED |
| Object | the galaxy |
—
|
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: the galaxy | Statement: [Deadliest Woman in the Galaxy, scopeOfEpithet, the galaxy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfEpithet Context triple: [Deadliest Woman in the Galaxy, scopeOfEpithet, the galaxy]
-
A.
epithetScope
chosen
Indicates that an epithet (a descriptive label or phrase) applies specifically within a defined contextual scope or domain for the referenced entity or relation.
-
B.
basisOfEpithet
Indicates that one entity serves as the reason or source for an epithet or descriptive name applied to another entity.
-
C.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
D.
associatedWithEpithet
Indicates that an entity is linked to or described by a particular epithet or descriptive label.
-
E.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6614566d88190aa5973e73819cf18 |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:57 a.m.