Triple
T12558924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Home |
E295288
|
entity |
| Predicate | appointedAsJudge |
P8553
|
FINISHED |
| Object | 1752-00-00 |
—
|
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: 1752-00-00 | Statement: [Henry Home, appointedAsJudge, 1752-00-00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appointedAsJudge Context triple: [Henry Home, appointedAsJudge, 1752-00-00]
-
A.
appointedAs
chosen
Indicates that one entity is formally assigned or designated to hold a specific role, position, or title in relation to another entity.
-
B.
appointedIn
Indicates that an entity is formally assigned or designated to a role, position, or office within a specific context, organization, or jurisdiction.
-
C.
appointedUnder
Indicates that one entity was formally given a position, role, or responsibility according to the authority, rules, or provisions established by another entity or legal framework.
-
D.
appointedOver
Indicates that one entity has been formally assigned authority, responsibility, or a supervisory role over another entity.
-
E.
appointedWith
Indicates that one entity has been formally assigned or designated to a role, position, or responsibility 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_69d6ad9cac2c81908e8a7bed82d1e21d |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95f5507b481908d13cc317b7402f6 |
completed | April 10, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69d95410d0b0819097646edd1b837104 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 11:48 p.m.