Triple
T7433047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanfrecce Hiroshima |
E171537
|
entity |
| Predicate | mottoOrigin |
P47757
|
FINISHED |
| Object | Mōri Motonari’s three arrows parable |
—
|
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: Mōri Motonari’s three arrows parable | Statement: [Sanfrecce Hiroshima, mottoOrigin, Mōri Motonari’s three arrows parable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mottoOrigin Context triple: [Sanfrecce Hiroshima, mottoOrigin, Mōri Motonari’s three arrows parable]
-
A.
mottoDerivedFrom
Indicates that one motto is derived, adapted, or taken from another source, such as a phrase, text, or earlier motto.
-
B.
mottoOriginal
Indicates that one entity is the original wording or form of another entity’s motto.
-
C.
hasMottoOrigin
chosen
Indicates that a motto originates from, or is derived from, a particular source, place, or context.
-
D.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
E.
mottoAuthor
Indicates that one entity is the creator or originator of the motto associated 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_69c68a63491881909281f73d4d5643bf |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f325ea908190b668fd4ce646f1e6 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f038582c8190bac77c9b5a34b862 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:12 p.m.