Triple
T37880635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hagoromo |
E944855
|
entity |
| Predicate | wakiRole |
P189566
|
FINISHED |
| Object | fisherman |
—
|
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: fisherman | Statement: [Hagoromo, wakiRole, fisherman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wakiRole Context triple: [Hagoromo, wakiRole, fisherman]
-
A.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
B.
roleInShinKokinWakashu
Indicates the specific role or involvement an entity has in relation to the Shin Kokin Wakashū (e.g., as compiler, editor, or contributor).
-
C.
ToshiRole
Indicates a role or function that an entity holds specifically within the context of Toshi.
-
D.
wowRole
Indicates that one entity has a specific role or function in the context of World of Warcraft with respect to another entity.
-
E.
roleInJakII
Indicates that an entity has a specific role or function within the context of the game Jak II.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.