Triple
T15473018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Cause |
E376710
|
entity |
| Predicate | hasLegalProcess |
P3010
|
FINISHED |
| Object | feudal arbitration |
—
|
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: feudal arbitration | Statement: [Great Cause, hasLegalProcess, feudal arbitration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalProcess Context triple: [Great Cause, hasLegalProcess, feudal arbitration]
-
A.
hasLegalProceeding
chosen
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
B.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
C.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
D.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
E.
hasLegalForceIn
Indicates that something (such as a law, regulation, or agreement) is legally valid, binding, and enforceable within a specified jurisdiction or context.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.