Triple
T14589320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recorder (judge) |
E342401
|
entity |
| Predicate | canContinuePracticeAs |
P89206
|
FINISHED |
| Object | barrister |
—
|
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: barrister | Statement: [Recorder (judge), canContinuePracticeAs, barrister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canContinuePracticeAs Context triple: [Recorder (judge), canContinuePracticeAs, barrister]
-
A.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
B.
licensedToPractice
chosen
Indicates that an entity has been officially authorized by a relevant authority to perform a particular professional practice or activity.
-
C.
approvedPractice
Indicates that a particular practice, method, or procedure has been formally reviewed and granted official approval for use or adoption.
-
D.
endedPracticeOf
Indicates that one entity caused another entity to stop or discontinue a particular practice or activity.
-
E.
requiresPractice
Indicates that performing or mastering one entity depends on engaging in repeated practice or training involving another entity.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4237d88819097f3f9a40f5be152 |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:24 a.m.