Triple
T30383636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana |
E772891
|
entity |
| Predicate | summoningSystem |
P138187
|
FINISHED |
| Object | Fate/Grand Order mobile game |
—
|
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: Fate/Grand Order mobile game | Statement: [Ana, summoningSystem, Fate/Grand Order mobile game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summoningSystem Context triple: [Ana, summoningSystem, Fate/Grand Order mobile game]
-
A.
summoned
Indicates that one entity has called forth, invoked, or ordered the appearance of another entity, typically through authority, command, or supernatural means.
-
B.
summonedIn
Indicates that one entity is called forth, invoked, or brought into presence within the context, location, or event represented by another entity.
-
C.
summonedAt
Indicates the time or place at which an entity is called, invoked, or brought into presence, typically by another agent or process.
-
D.
methodOfSummoning
chosen
Indicates the specific way or procedure by which an entity is called forth, invoked, or brought into presence.
-
E.
hasRitualSystem
Indicates that an entity possesses or is associated with a structured set of rituals or ceremonial practices.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6851c44108190822e8d70e1114e09 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.