Triple
T30382618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphonse Elric |
E772869
|
entity |
| Predicate | soulBoundBy |
P68132
|
FINISHED |
| Object | Edward Elric |
—
|
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: Edward Elric | Statement: [Alphonse Elric, soulBoundBy, Edward Elric]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soulBoundBy Context triple: [Alphonse Elric, soulBoundBy, Edward Elric]
-
A.
bondedWith
chosen
Indicates that two entities are joined by a strong, enduring connection or attachment, whether emotional, social, or structural.
-
B.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
C.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
-
D.
associatedWithPositionThroughSoul
Indicates a relationship where an entity’s position, role, or placement is determined or influenced through its soul or spiritual essence.
-
E.
sharesTelepathicBondWith
Indicates a mutual telepathic connection through which two entities can directly share thoughts, feelings, or information.
- 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_69f6851aeb948190b674200cf6bf51f9 |
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.