Triple
T32877821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The High Judge |
E840974
|
entity |
| Predicate | temporalScopeOfJudgment |
P105718
|
FINISHED |
| Object | all of human history |
—
|
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: all of human history | Statement: [The High Judge, temporalScopeOfJudgment, all of human history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalScopeOfJudgment Context triple: [The High Judge, temporalScopeOfJudgment, all of human history]
-
A.
temporal scope
chosen
Indicates the time period or duration over which a particular relationship, condition, or fact holds true.
-
B.
hasTemporalJurisdictionFrom
Indicates that an authority’s jurisdiction or control over something begins at a specified point in time.
-
C.
jurisdictionPeriod
Indicates the time span during which a particular authority or entity holds legal or official jurisdiction over something.
-
D.
temporalAspect
Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
-
E.
temporality
Indicates the time-related relationship between events or states, such as their order, duration, or simultaneity.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:18 a.m.