Triple
T25020433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zafar Khan Muzaffar |
E626554
|
entity |
| Predicate | startTimeOfRule |
P21305
|
FINISHED |
| Object | late 14th century |
—
|
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: late 14th century | Statement: [Zafar Khan Muzaffar, startTimeOfRule, late 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfRule Context triple: [Zafar Khan Muzaffar, startTimeOfRule, late 14th century]
-
A.
endTimeOfRule
Indicates the specific time at which a given rule ceases to be in effect or valid.
-
B.
startTimeOfRuleInHanover
Indicates the specific time at which a particular rule or regulation becomes effective or applicable within Hanover.
-
C.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
D.
startOfRule
chosen
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
-
E.
startTimeAsCardinal
Indicates the specific clock time at which an event or action begins, expressed as a cardinal (numeric) value rather than a textual or formatted time.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 18, 2026, 6:06 a.m.