Triple
T31528615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | general obligations |
E804411
|
entity |
| Predicate | mayBeImpliedBy |
P72358
|
FINISHED |
| Object | law |
—
|
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: law | Statement: [general obligations, mayBeImpliedBy, law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeImpliedBy Context triple: [general obligations, mayBeImpliedBy, law]
-
A.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
B.
impliesAttribute
Indicates that the presence or occurrence of one property, condition, or relation logically entails the existence or truth of another attribute.
-
C.
hasImplicationsFor
Indicates that one entity’s state, action, or condition leads to consequences, effects, or relevance for another entity.
-
D.
isAssumedIn
Indicates that something is taken for granted or presumed to hold within a particular context, without requiring explicit proof or verification.
-
E.
mayEntail
chosen
Indicates that one statement or condition can logically lead to or imply the truth of another, without guaranteeing it.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 30, 2026, 10 p.m.