Triple
T17518495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amarr Empire |
E426625
|
entity |
| Predicate | lawBasedOn |
P125
|
FINISHED |
| Object | religious doctrine |
—
|
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: religious doctrine | Statement: [Amarr Empire, lawBasedOn, religious doctrine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawBasedOn Context triple: [Amarr Empire, lawBasedOn, religious doctrine]
-
A.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
C.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
D.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
E.
legalCodePromulgatedBy
Indicates that a specific legal code was formally issued or enacted by a particular authority or governing body.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d0daa48190be69aff32b0324bc |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.