Triple
T160768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court Chamber |
E3279
|
entity |
| Predicate | eraOfUse |
P3656
|
FINISHED |
| Object | late 18th 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 18th century | Statement: [Supreme Court Chamber, eraOfUse, late 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfUse Context triple: [Supreme Court Chamber, eraOfUse, late 18th century]
-
A.
era
Indicates that something existed, occurred, or was valid during a specified historical or temporal period.
-
B.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
C.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
E.
yearDescribed
Indicates the year in which something (typically a species, object, or concept) was formally described or documented.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25856d934819095460b2ea566eb6b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256623704819089d9eeefe05858ce |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.