Triple
T38702933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | go-sekke |
E950187
|
entity |
| Predicate | monopolizedOffice |
P191662
|
FINISHED |
| Object | regent to the Japanese emperor |
—
|
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: regent to the Japanese emperor | Statement: [go-sekke, monopolizedOffice, regent to the Japanese emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monopolizedOffice Context triple: [go-sekke, monopolizedOffice, regent to the Japanese emperor]
-
A.
controlledOffice
Indicates that one entity has authority over, manages, or directs the operations of a particular office or administrative location.
-
B.
overseesOffice
Indicates that one entity has managerial or supervisory responsibility for the operations or activities of a particular office.
-
C.
establishedOffice
Indicates that an entity created or set up an official office or place of operation.
-
D.
isPermanentOffice
Indicates that an office or position is established on a lasting, ongoing basis rather than being temporary or time-limited.
-
E.
mainOffice
Indicates that one location or office serves as the primary or central office for an organization or entity.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce54532948190a5cfacfe18e09322 |
completed | May 7, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:33 p.m.