Triple
T36957282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FormGen |
E914219
|
entity |
| Predicate | roleInSpearOfDestiny |
P203707
|
FINISHED |
| Object | publisher |
—
|
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: publisher | Statement: [FormGen, roleInSpearOfDestiny, publisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSpearOfDestiny Context triple: [FormGen, roleInSpearOfDestiny, publisher]
-
A.
roleInFateZero
Indicates that an entity has a specific narrative or functional role within the context of the Fate/Zero series.
-
B.
roleInFateStayNight
Indicates the narrative role or function an entity has within the story of Fate/stay night.
-
C.
roleInFableIII
Indicates that an entity has a specific role or function within the context of the work "Fable III."
-
D.
roleInBladeTrinity
Indicates that an entity participated in the movie "Blade: Trinity" in a specific role (such as actor, director, or crew position).
-
E.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
| PDg | Predicate description generation | batch_6a01cb8914048190a5e60e5639b1f88b |
completed | May 11, 2026, 12:28 p.m. |
Created at: May 3, 2026, 4:13 p.m.