Triple
T30584777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musashi Province |
E778474
|
entity |
| Predicate | importantCenterFor |
P45017
|
FINISHED |
| Object | politics |
—
|
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: politics | Statement: [Musashi Province, importantCenterFor, politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantCenterFor Context triple: [Musashi Province, importantCenterFor, politics]
-
A.
importantSaint
Indicates that the subject is recognized as a particularly significant or highly revered saint within a religious or spiritual tradition.
-
B.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
C.
historicallyImportantCenter
chosen
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
D.
isSocialCenterOf
Indicates that one entity serves as the primary gathering place or hub for social activities and interactions for another entity or group.
-
E.
importantObject
Indicates that one entity is considered especially significant, central, or of high priority in relation to another entity or context.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 8:23 p.m.