Triple
T160774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court Chamber |
E3279
|
entity |
| Predicate | hasOriginalUse |
P2506
|
FINISHED |
| Object | meeting place of the U.S. Supreme Court |
—
|
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: meeting place of the U.S. Supreme Court | Statement: [Supreme Court Chamber, hasOriginalUse, meeting place of the U.S. Supreme Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalUse Context triple: [Supreme Court Chamber, hasOriginalUse, meeting place of the U.S. Supreme Court]
-
A.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
B.
hasSurvivingOriginals
Indicates that some of the original instances or versions of an entity still exist and have not been lost, destroyed, or replaced.
-
C.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
D.
isUsedAs
chosen
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
E.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
- 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.