Triple
T32642250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shark God |
E834511
|
entity |
| Predicate | fictionalProgenitorOf |
P195975
|
FINISHED |
| Object | King Shark |
—
|
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: King Shark | Statement: [Shark God, fictionalProgenitorOf, King Shark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalProgenitorOf Context triple: [Shark God, fictionalProgenitorOf, King Shark]
-
A.
fictionalOrigin
Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
-
B.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
C.
fictionalAuthorOrigin
Indicates that a fictional author character originates from, or is associated with, a particular place or region.
-
D.
isFictionallyCreatedBy
Indicates that an entity is a fictional creation authored, invented, or brought into existence within a narrative by another entity.
-
E.
fictionalGrandfather
Indicates that one entity is the fictional grandfather (a grandfather character within a story or fictional universe) of another entity.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: May 1, 2026, 1:07 a.m.