Triple
T30347066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | True Cross Order |
E771893
|
entity |
| Predicate | leaderInJapan |
P178069
|
FINISHED |
| Object | Mephisto Pheles |
—
|
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: Mephisto Pheles | Statement: [True Cross Order, leaderInJapan, Mephisto Pheles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderInJapan Context triple: [True Cross Order, leaderInJapan, Mephisto Pheles]
-
A.
commanderJapan
Indicates that an entity serves as the military commander of Japan or of Japanese forces.
-
B.
JapanCaptain
Indicates that an entity serves as the captain or leading representative of a Japanese team, group, or delegation.
-
C.
successorInJapan
Indicates that one entity directly follows or replaces another in a role, position, or sequence within the context of Japan.
-
D.
founderInJapan
Indicates that an entity is the founder of something (such as an organization or company) specifically in Japan.
-
E.
lastDaimyo
Indicates that the subject is the final or most recent daimyo (feudal lord) to hold authority over the object.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 29, 2026, 7:56 p.m.