Triple
T24935064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyotomi Japan |
E623290
|
entity |
| Predicate | hasCenterOfPower |
P112282
|
FINISHED |
| Object | Osaka Castle |
—
|
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: Osaka Castle | Statement: [Toyotomi Japan, hasCenterOfPower, Osaka Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCenterOfPower Context triple: [Toyotomi Japan, hasCenterOfPower, Osaka Castle]
-
A.
hasPowerBase
chosen
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
B.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
C.
hasCorePower
Indicates that an entity possesses a primary or fundamental power, ability, or capability that defines its essential function or role.
-
D.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
-
E.
hasCentralAct
Indicates that an entity includes or is characterized by a primary or most important action, event, or operation at its core.
- 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_69e2fac6b5a48190a1c38857f00915a9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f423d4043c8190952356417e9b504c |
completed | May 1, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:30 a.m.