Triple
T17609850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Samuel Romilly |
E428937
|
entity |
| Predicate | wasCalledToTheBar |
P48477
|
FINISHED |
| Object | 1783 |
—
|
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: 1783 | Statement: [Sir Samuel Romilly, wasCalledToTheBar, 1783]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCalledToTheBar Context triple: [Sir Samuel Romilly, wasCalledToTheBar, 1783]
-
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.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wasA
Indicates that an entity previously had a certain role, type, or classification in the past.
-
D.
wasHeldToBe
Indicates that an authority or decision-maker formally judged or determined something to have a particular status, quality, or legal meaning.
-
E.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4e6ba48190804e113983e7c704 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:51 a.m.