Triple
T185459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Syndics of the Drapers’ Guild |
E3969
|
entity |
| Predicate | subjectRole |
P268
|
FINISHED |
| Object | guild officials |
—
|
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: guild officials | Statement: [The Syndics of the Drapers’ Guild, subjectRole, guild officials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectRole Context triple: [The Syndics of the Drapers’ Guild, subjectRole, guild officials]
-
A.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
-
C.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
D.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.