Triple
T25875894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xin dynasty |
E651899
|
entity |
| Predicate | claimedPrecedent |
P162604
|
FINISHED |
| Object | Zhou dynasty institutions |
—
|
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: Zhou dynasty institutions | Statement: [Xin dynasty, claimedPrecedent, Zhou dynasty institutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimedPrecedent Context triple: [Xin dynasty, claimedPrecedent, Zhou dynasty institutions]
-
A.
precedentChallenged
Indicates that an existing legal precedent is being questioned, disputed, or formally contested.
-
B.
typicalPrecedent
Indicates that one situation, case, or event serves as a standard or commonly followed example for how similar later situations are handled.
-
C.
claimedPrinciple
Indicates that an entity has asserted or stated a particular principle as true, valid, or guiding.
-
D.
modifiedPrecedent
Indicates that one entity has altered, qualified, or changed the terms, scope, or interpretation of a prior decision, rule, or precedent.
-
E.
precedentInterpreted
Indicates that one legal precedent is interpreted or understood in a particular way, often as clarified or applied in subsequent decisions or analyses.
- 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 22, 2026, 8:12 a.m.