Triple
T30686983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of the Lord High Steward |
E781211
|
entity |
| Predicate | trialParticipants |
P2434
|
FINISHED |
| Object | peerage as jury |
—
|
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: peerage as jury | Statement: [Court of the Lord High Steward, trialParticipants, peerage as jury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialParticipants Context triple: [Court of the Lord High Steward, trialParticipants, peerage as jury]
-
A.
surveyParticipants
Indicates that certain entities take part in or respond to a survey.
-
B.
participantRecruitmentStart
Indicates the point in time when the process of recruiting or enrolling participants for a study, event, or activity begins.
-
C.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
D.
partnerInStudyWith
Indicates that two entities are collaborators or co-participants in the same study or research project.
-
E.
secondaryParticipants
Indicates that certain entities participate in an event or activity in a supporting or non-primary role alongside the main participants.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b84caf08190b7255b42012d749e |
completed | May 2, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:33 p.m.