Triple
T30344299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monthly Shōnen Gangan |
E771832
|
entity |
| Predicate | notableForSerializing |
P207230
|
FINISHED |
| Object | Fullmetal Alchemist |
E215042
|
NE 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: Fullmetal Alchemist | Statement: [Monthly Shōnen Gangan, notableForSerializing, Fullmetal Alchemist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForSerializing Context triple: [Monthly Shōnen Gangan, notableForSerializing, Fullmetal Alchemist]
-
A.
notableField
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
D.
notableKey
Indicates that the referenced key is of particular importance or prominence compared to other keys in the same context.
-
E.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
- F. None of above. chosen
Provenance (5 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277c2737348190b3dc8979f853cd3a |
completed | June 9, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 7:55 p.m.