Triple
T670926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House simple resolution |
E12968
|
entity |
| Predicate | hasForceOfLaw |
P6506
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [House simple resolution, hasForceOfLaw, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasForceOfLaw Context triple: [House simple resolution, hasForceOfLaw, no]
-
A.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
B.
hasLegalEffect
chosen
Indicates that an action, document, or condition produces recognized legal consequences or enforceable rights and obligations.
-
C.
legalAct
Indicates that an entity performs, enacts, or is involved in a formal legal action, measure, or proceeding under a legal framework.
-
D.
obeysLaw
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
-
E.
hasLegalInstrument
Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a1b3682c8190a9b9a454480c3446 |
completed | March 1, 2026, 8:29 p.m. |
| PD | Predicate disambiguation | batch_69a49d1a16c48190af89e3b078a4957e |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.