Triple
T20933828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dulo |
E515532
|
entity |
| Predicate | endOfRuleApprox |
P14957
|
FINISHED |
| Object | mid-8th 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: mid-8th century | Statement: [Dulo, endOfRuleApprox, mid-8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfRuleApprox Context triple: [Dulo, endOfRuleApprox, mid-8th century]
-
A.
endRule
chosen
Indicates that a previously active rule, regulation, or governing condition is terminated or ceases to apply.
-
B.
typicalEndRule
Indicates the rule or condition that normally determines how or when a process, event, or relationship comes to an end.
-
C.
reasonForEndOfRule
Indicates the cause, circumstance, or event that led to the termination or conclusion of a particular rule or period of rule.
-
D.
endOfRuleContext
Indicates that a particular parsing or evaluation rule has reached its terminating boundary within the current context.
-
E.
startOfRule
Indicates that one element marks the beginning boundary or initial segment of a specified rule.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f94fc194819099df82357a7f33c7 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.