Triple
T7697874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas state law |
E174412
|
entity |
| Predicate | hasPrecedentSystem |
P15038
|
FINISHED |
| Object | common law |
—
|
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: common law | Statement: [Texas state law, hasPrecedentSystem, common law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrecedentSystem Context triple: [Texas state law, hasPrecedentSystem, common law]
-
A.
precedentSystem
chosen
Indicates that one legal system or framework serves as a source of precedent or authoritative guidance for another system.
-
B.
hasCourtPrecedence
Indicates that one court decision or ruling holds authoritative priority over another in legal reasoning or application.
-
C.
hasPrecedenceSystem
Indicates that one system is defined as having priority or a higher order of precedence over another system in determining outcomes or rules.
-
D.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
-
E.
hasPrecedentialStatus
Indicates that one legal decision or authority possesses a recognized level of precedential force or binding effect relative to others.
- 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_69c6995a72cc8190998e56daa6f8e453 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c70165e78c8190bf6b3c34e243cb81 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:03 p.m.