Triple
T24798361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Timothy Love |
E620451
|
entity |
| Predicate | hasLegalStandingIn |
P157836
|
FINISHED |
| Object | Obergefell v. Hodges |
—
|
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: Obergefell v. Hodges | Statement: [Timothy Love, hasLegalStandingIn, Obergefell v. Hodges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalStandingIn Context triple: [Timothy Love, hasLegalStandingIn, Obergefell v. Hodges]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
hasHighestLegalStatusWithinCountry
Indicates that an entity holds the topmost legally recognized status or rank within a specific country, above all other comparable statuses.
-
C.
legalStandingBasis
Indicates the legal grounds or justification on which a party’s standing or authority in a legal matter is based.
-
D.
hasLegalRank
Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
-
E.
hasLegalAuthorityFrom
Indicates that one entity possesses formal legal power, rights, or authorization that originates from or is granted by another 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 4:49 a.m.