Triple
T27199102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maranaw |
E683685
|
entity |
| Predicate | hasNotableEpic |
P196618
|
FINISHED |
| Object | Darangen |
—
|
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: Darangen | Statement: [Maranaw, hasNotableEpic, Darangen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEpic Context triple: [Maranaw, hasNotableEpic, Darangen]
-
A.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
B.
hasNotableFable
Indicates that an entity is associated with a well-known or significant fable, either as its subject, source, or key element.
-
C.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
-
D.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
E.
hasNarrativeArcIn
Indicates that an entity’s storyline or narrative progression occurs within or is contained by a specified work, context, or medium.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: April 27, 2026, 9:35 a.m.