Triple
T13126490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotaki |
E311855
|
entity |
| Predicate | timeOfRuleEnd |
P86333
|
FINISHED |
| Object | 1738 |
—
|
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: 1738 | Statement: [Hotaki, timeOfRuleEnd, 1738]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfRuleEnd Context triple: [Hotaki, timeOfRuleEnd, 1738]
-
A.
endTimeAsCapital
Indicates that a specified time marks the ending point of an event, process, or state in the role of its designated capital or primary endpoint.
-
B.
timeOfSettingEnd
chosen
Indicates the point in time at which a specified setting, condition, or configuration ceases to be in effect.
-
C.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
D.
temporalAuthorityEndedBy
Indicates that a period of temporal authority or secular power held by one entity comes to an end as a result of an action or event caused by another entity.
-
E.
statusEndsWhen
Indicates that a particular status or condition ceases to hold when a specified event, time, or state occurs.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.