Triple
T19929008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naboth |
E479001
|
entity |
| Predicate | legalBasisForRefusal |
P125
|
FINISHED |
| Object | Mosaic law on ancestral land |
—
|
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: Mosaic law on ancestral land | Statement: [Naboth, legalBasisForRefusal, Mosaic law on ancestral land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBasisForRefusal Context triple: [Naboth, legalBasisForRefusal, Mosaic law on ancestral land]
-
A.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
C.
legalBasisWeakenedBy
Indicates that the legal force, validity, or effectiveness of something is reduced or undermined by another factor, action, or decision.
-
D.
legalStatusDenied
Indicates that an entity has been refused or not granted a particular legal status or recognition.
-
E.
legalStandingBasis
Indicates the legal grounds or justification on which a party’s standing or authority in a legal matter is based.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659cd4500819090363a4b7d6bf193 |
completed | April 20, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.