Triple
T25201493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greed (Fullmetal Alchemist: Brotherhood, English dub) |
E631135
|
entity |
| Predicate | laterAllies |
P61003
|
FINISHED |
| Object | Ling Yao |
—
|
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: Ling Yao | Statement: [Greed (Fullmetal Alchemist: Brotherhood, English dub), laterAllies, Ling Yao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAllies Context triple: [Greed (Fullmetal Alchemist: Brotherhood, English dub), laterAllies, Ling Yao]
-
A.
laterAlliesWith
chosen
Indicates that two entities become allies at a later time, after not being allied initially.
-
B.
majorAllies
Indicates that the entities are principal or primary allies, signifying a strong, significant, and mutually supportive alliance between them.
-
C.
alliesInWar
Indicates that two or more parties are cooperating as allies on the same side in a specific war or armed conflict.
-
D.
historicallyAlliedWith
Indicates that two entities have been political, military, or strategic allies during some period in the past.
-
E.
alliesOf
Indicates that one entity is in a cooperative, supportive, or mutually beneficial alliance with another entity.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 12:51 p.m.