Triple
T31649403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fathom |
E807675
|
entity |
| Predicate | protagonistSpeciesOrOrigin |
P39813
|
FINISHED |
| Object | member of the Blue |
—
|
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: member of the Blue | Statement: [Fathom, protagonistSpeciesOrOrigin, member of the Blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistSpeciesOrOrigin Context triple: [Fathom, protagonistSpeciesOrOrigin, member of the Blue]
-
A.
protagonistSpecies
chosen
Indicates that an entity is the species or kind of creature to which the protagonist of a story or scenario belongs.
-
B.
protagonistOrigin
Indicates that one entity is the origin, source, or starting point of the protagonist in a narrative or story.
-
C.
protagonistHomeworld
Indicates the homeworld or place of origin associated with a story’s main protagonist.
-
D.
originSpecies
Indicates that one entity is the original or source species from which another entity is derived, evolved, or produced.
-
E.
protagonistFamilyOrigin
Indicates that a character’s family background, ancestry, or place of origin is associated with the story’s protagonist.
- 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 30, 2026, 10:52 p.m.