Triple
T1349272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bourke v. Beshear |
E28843
|
entity |
| Predicate | circuitHolding |
P26869
|
FINISHED |
| Object | upheld Kentucky’s same-sex marriage bans |
—
|
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: upheld Kentucky’s same-sex marriage bans | Statement: [Bourke v. Beshear, circuitHolding, upheld Kentucky’s same-sex marriage bans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circuitHolding Context triple: [Bourke v. Beshear, circuitHolding, upheld Kentucky’s same-sex marriage bans]
-
A.
hasCircuit
Indicates that an entity is equipped with, contains, or is associated with an electrical or logical circuit.
-
B.
circuit
Indicates that one entity forms or participates in an electrical or logical pathway that allows current or signals to flow through a connected system involving another entity.
-
C.
circuitType
Indicates the specific kind or category of electrical circuit associated with an entity.
-
D.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
E.
isUsuallyHeldBy
Indicates that something is most commonly or typically possessed, carried, or controlled by a particular entity.
- F. None of above. chosen
Provenance (4 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c268745481908be649526c18e558 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:56 p.m.