Triple
T33894091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Girdlers |
E868855
|
entity |
| Predicate | hasLiverymen |
P196671
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Worshipful Company of Girdlers, hasLiverymen, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiverymen Context triple: [Worshipful Company of Girdlers, hasLiverymen, yes]
-
A.
hasWorshipfulCompanyRank
Indicates that an entity holds a specific rank or position within a Worshipful Company (a livery company or similar guild-like organization).
-
B.
hasLiveryRank
Indicates that an entity holds a specific rank or level within a livery or hierarchical service organization.
-
C.
hasHeraldicOfficer
Indicates that an entity is associated with or served by a specific heraldic officer responsible for its coats of arms or heraldic matters.
-
D.
liveryType
Indicates the specific style, design, or branding scheme applied to an entity’s exterior appearance.
-
E.
hasLivery
Indicates that one entity bears or displays the distinctive colors, markings, or branding (livery) associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69fe610d75a48190bfd08a9bb957fcd3 |
completed | May 8, 2026, 10:17 p.m. |
Created at: May 1, 2026, 1:48 a.m.