Triple
T23673777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimazu clan |
E584809
|
entity |
| Predicate | retainedControlUntil |
P128856
|
FINISHED |
| Object | Meiji Restoration |
—
|
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: Meiji Restoration | Statement: [Shimazu clan, retainedControlUntil, Meiji Restoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retainedControlUntil Context triple: [Shimazu clan, retainedControlUntil, Meiji Restoration]
-
A.
continuesToControl
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
B.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
C.
controlledAfter
Indicates that one entity gains or maintains control over another entity only after a specified time, event, or condition has occurred.
-
D.
controlledByAtEnd
chosen
Indicates that one entity has control or governing authority over another entity at the final point or conclusion of a specified process, period, or event.
-
E.
transferredControlFrom
Indicates that authority or control over something has been moved or handed over from one entity to another.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f1dee08190bfe78564c65f01ad |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.