Triple
T4823913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir William Collyer |
E107774
|
entity |
| Predicate | professionContext |
P24248
|
FINISHED |
| Object | English legal system |
—
|
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: English legal system | Statement: [Sir William Collyer, professionContext, English legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionContext Context triple: [Sir William Collyer, professionContext, English legal system]
-
A.
employmentContext
Indicates the situational or organizational setting in which an employment relationship or work activity takes place.
-
B.
professionalScope
Indicates the range of activities, responsibilities, or roles that fall within a person’s or organization’s recognized professional duties or expertise.
-
C.
businessCareer
Indicates a relationship where an entity’s professional life, roles, or progression is specifically within the field of business or commerce.
-
D.
careerField
chosen
Indicates the professional domain or occupational area in which an entity works or specializes.
-
E.
professional
Indicates that one entity has a formal, occupation-related role, service, or expertise in relation to 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.