Triple
T35479402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tozama domain |
E1025426
|
entity |
| Predicate | hasRiskPerceptionByShogunate |
P165534
|
FINISHED |
| Object | potentially disloyal |
—
|
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: potentially disloyal | Statement: [tozama domain, hasRiskPerceptionByShogunate, potentially disloyal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiskPerceptionByShogunate Context triple: [tozama domain, hasRiskPerceptionByShogunate, potentially disloyal]
-
A.
hasRiskFrom
Indicates that one entity is exposed to or may suffer potential harm, loss, or adverse effects as a result of another entity.
-
B.
viewedAsRiskBy
chosen
Indicates that one entity is perceived or considered as a potential risk or threat by another entity.
-
C.
hasPerception
Indicates that one entity is aware of, senses, or recognizes another entity or phenomenon.
-
D.
riskBelief
Indicates that an entity holds a belief or assessment about the likelihood or severity of a potential risk associated with another entity, event, or situation.
-
E.
riskSensitivity
Indicates how strongly an entity’s decisions or behavior change in response to potential risk or uncertainty.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:04 p.m.