Triple
T37879704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamana Sōzen |
E944836
|
entity |
| Predicate | helpedInitiate |
P1408
|
FINISHED |
| Object | Sengoku period |
—
|
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: Sengoku period | Statement: [Yamana Sōzen, helpedInitiate, Sengoku period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedInitiate Context triple: [Yamana Sōzen, helpedInitiate, Sengoku period]
-
A.
initiatedIn
Indicates that an action, process, or event was started or first brought into effect within a specified context, such as a place, time, or situation.
-
B.
initiatedBecauseOf
Indicates that one event, action, or process was started as a direct result of, or in response to, another specified cause or condition.
-
C.
possiblyInitiatedBy
Indicates that an event or state may have been initiated or caused by a particular entity, but this initiating role is uncertain or not definitively established.
-
D.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
E.
initiatedOver
Indicates that one entity has begun or set in motion an action, process, or event that affects or concerns 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.