Triple
T31528631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | general obligations |
E804411
|
entity |
| Predicate | mayAriseIn |
P48990
|
FINISHED |
| Object | tort 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: tort law | Statement: [general obligations, mayAriseIn, tort law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAriseIn Context triple: [general obligations, mayAriseIn, tort law]
-
A.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
B.
arisesIn
chosen
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
C.
mayAppear
Indicates that an entity is allowed or has the possibility to be present or occur in association with another entity or context.
-
D.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
E.
mayAlsoOriginateFrom
Indicates that something has an additional possible source or origin beyond its primary or known one.
- 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_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10 p.m.