Triple
T7765787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Cockburn, Lord Cockburn |
E176140
|
entity |
| Predicate | calledToBar |
P48477
|
FINISHED |
| Object | 1800 |
—
|
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: 1800 | Statement: [Henry Cockburn, Lord Cockburn, calledToBar, 1800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: calledToBar Context triple: [Henry Cockburn, Lord Cockburn, calledToBar, 1800]
-
A.
calledToTheBarAt
chosen
Indicates that a person has been formally admitted and authorized to practice as a barrister by a specific legal institution or jurisdiction at a certain time.
-
B.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
C.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
D.
appointedFor
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
E.
holderCalled
Indicates that one entity, acting as a holder or possessor, initiated a phone call or communication 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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7043279748190b30882e9cc6cca54 |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:09 p.m.