Triple
T9627996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boswell family |
E232518
|
entity |
| Predicate | relatedFieldOfActivity |
P3
|
FINISHED |
| Object | 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: law | Statement: [Boswell family, relatedFieldOfActivity, law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedFieldOfActivity Context triple: [Boswell family, relatedFieldOfActivity, law]
-
A.
relatedWorkField
Indicates that one work is associated with or pertains to the same or a relevant field, discipline, or area of activity as another work.
-
B.
possibleFieldOfActivity
Indicates that something is a potential or suitable area in which an entity can operate, work, or be active.
-
C.
workRelatedTo
Indicates a relationship where one entity’s work, tasks, or professional activities are connected, associated, or relevant to those of another entity.
-
D.
relatedField
Indicates that one field, topic, or area of study is connected or relevant to another in subject matter or application.
-
E.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.