Triple
T26066710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Baron Passfield |
E657421
|
entity |
| Predicate | titleHolderMemberOf |
P62657
|
FINISHED |
| Object | Fabian Society |
—
|
NE NERFINISHED |
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: Fabian Society | Statement: [1st Baron Passfield, titleHolderMemberOf, Fabian Society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderMemberOf Context triple: [1st Baron Passfield, titleHolderMemberOf, Fabian Society]
-
A.
titleHolderBelongsTo
chosen
Indicates that the holder of a title is associated with or belongs to a particular entity, such as an organization, position, or domain.
-
B.
titleHolderRelationship
Indicates a relationship where one entity holds, possesses, or bears a specific title in connection to another entity or context.
-
C.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
D.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
E.
memberTitle
Indicates the formal title or designation held by a member within a group, organization, or body.
- 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_69ee5bbe539081909efc7f9dd7c1b53c |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 26, 2026, 7:24 p.m.