Triple
T14937293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parr family |
E372427
|
entity |
| Predicate | memberServedAs |
P1827
|
FINISHED |
| Object | lady-in-waiting at Tudor court |
—
|
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: lady-in-waiting at Tudor court | Statement: [Parr family, memberServedAs, lady-in-waiting at Tudor court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: memberServedAs Context triple: [Parr family, memberServedAs, lady-in-waiting at Tudor court]
-
A.
servedAs
chosen
Indicates that one entity held and performed the role, position, or function associated with another entity for some period of time.
-
B.
formerMemberOf
Indicates that an entity once belonged to or was affiliated with a group, organization, or body, but is no longer a member.
-
C.
memberHeldOfficeFrom
Indicates that a member began holding a particular office or position starting from a specified date or time.
-
D.
hasMemberWhoServedOn
Indicates that a group or organization includes at least one member who has served on a specified body, committee, or entity.
-
E.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64904d88190b6b4140da8e8199d |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:37 a.m.