Triple
T30382619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphonse Elric |
E772869
|
entity |
| Predicate | bloodSealLocation |
P169140
|
FINISHED |
| Object | inside armor |
—
|
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: inside armor | Statement: [Alphonse Elric, bloodSealLocation, inside armor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bloodSealLocation Context triple: [Alphonse Elric, bloodSealLocation, inside armor]
-
A.
bloodStatus
Indicates the classification of an entity based on the type or purity of its blood or lineage.
-
B.
bloodTypeRelativeToSystemicVeins
Indicates the relationship between blood and the systemic veins in terms of its type, characteristics, or classification within that venous system.
-
C.
woundLocation
Indicates the specific anatomical site on an entity’s body where a wound is present or occurred.
-
D.
Seal of the Mouth
Indicates a relationship in which one party is bound—formally or supernaturally—to keep silent and not reveal certain information.
-
E.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
- 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_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. |
| PDg | Predicate description generation | batch_69f679496c188190ba585792f987a1f4 |
completed | May 2, 2026, 10:23 p.m. |
Created at: April 29, 2026, 8:01 p.m.