Triple
T639303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Iron Lady |
E16696
|
entity |
| Predicate | associatedPersonRole |
P13957
|
FINISHED |
| Object | leader of the Conservative Party |
—
|
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: leader of the Conservative Party | Statement: [The Iron Lady, associatedPersonRole, leader of the Conservative Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonRole Context triple: [The Iron Lady, associatedPersonRole, leader of the Conservative Party]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
C.
organizationAssociatedWith
Indicates that there is a formal or recognized connection or affiliation between an organization and another entity.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
hasOrganizationalRole
chosen
Indicates that an entity holds a specific role, position, or function within an organization.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a17b125481909a6ab53424954792 |
completed | March 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69a49d0629308190bcc137639567f7c2 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.