Triple
T23591375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hughes Court |
E582485
|
entity |
| Predicate | knownForCase |
P124381
|
FINISHED |
| Object | West Coast Hotel Co. v. Parrish |
—
|
NE NERFINISHED |
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: West Coast Hotel Co. v. Parrish | Statement: [Hughes Court, knownForCase, West Coast Hotel Co. v. Parrish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCase Context triple: [Hughes Court, knownForCase, West Coast Hotel Co. v. Parrish]
-
A.
knownForDecision
chosen
Indicates that an entity is recognized or notable specifically for making a particular decision.
-
B.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
knownForStoryline
Indicates that an entity is recognized or notable specifically for its narrative or storyline.
-
E.
knownForAct
Indicates that an entity is recognized or notable for performing a particular act or action.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b035a5d88190bd2e1fa0170045cd |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.