Triple
T1440590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bostock v. Clayton County |
E31059
|
entity |
| Predicate | keyword |
P2309
|
FINISHED |
| Object | LGBTQ rights |
—
|
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: LGBTQ rights | Statement: [Bostock v. Clayton County, keyword, LGBTQ rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyword Context triple: [Bostock v. Clayton County, keyword, LGBTQ rights]
-
A.
keyTerm
chosen
Indicates that a term functions as a primary or central concept within a given context or information structure.
-
B.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
C.
keyFeature
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
D.
keySymbol
Indicates that one entity serves as the symbolic representation or notation used to denote another entity as a key.
-
E.
keyText
Indicates that a piece of text functions as a key or identifier used to access, reference, or unlock something in a system 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_69a4991633388190a4d61b5a98aa407a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.