Triple
T25092556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foss v Harbottle |
E628501
|
entity |
| Predicate | hasExceptionType |
P160096
|
FINISHED |
| Object | derivative action |
—
|
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: derivative action | Statement: [Foss v Harbottle, hasExceptionType, derivative action]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExceptionType Context triple: [Foss v Harbottle, hasExceptionType, derivative action]
-
A.
hasExceptionFor
Indicates that a general rule, condition, or behavior does not apply in a particular case or under specific circumstances.
-
B.
hasException
Indicates that a general rule, process, or condition does not apply in a particular case due to a specified exception.
-
C.
hasExceptionConstruct
Indicates that a construct or element is associated with, or defined by, a specific exception-handling construct (such as a try-catch or similar exception mechanism).
-
D.
haveExceptionMember
Indicates that an entity includes or is associated with a member that represents an exception to a rule, condition, or normal behavior.
-
E.
hasErrorType
Indicates that an entity is associated with, or classified by, a specific type or category of error.
- F. None of above. chosen
Provenance (4 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6018f91248190985323d1a678e539 |
completed | May 2, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 18, 2026, 6:24 a.m.