Triple
T23654553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkinson & Parkinson |
E584259
|
entity |
| Predicate | possibleField |
P153050
|
FINISHED |
| Object | law practice |
—
|
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 practice | Statement: [Parkinson & Parkinson, possibleField, law practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleField Context triple: [Parkinson & Parkinson, possibleField, law practice]
-
A.
possibleValue
Indicates that a given value is one of the allowed or valid options for a particular attribute, parameter, or variable.
-
B.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
C.
possibleElement
Indicates that something can potentially be a member, component, or constituent part of another entity or set, without asserting that it actually is.
-
D.
possiblePosition
Indicates that a given location or arrangement is a valid or allowable position for the entity within the specified context or constraints.
-
E.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35a513c8190a251fe2f55b23d7c |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f1233300bc8190ac1639bdca1d7d99 |
completed | April 28, 2026, 9:14 p.m. |
Created at: April 17, 2026, 6:49 p.m.