Triple
T33894094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Girdlers |
E868855
|
entity |
| Predicate | foundedAsCraftGuild |
P196753
|
FINISHED |
| Object | medieval period |
—
|
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: medieval period | Statement: [Worshipful Company of Girdlers, foundedAsCraftGuild, medieval period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsCraftGuild Context triple: [Worshipful Company of Girdlers, foundedAsCraftGuild, medieval period]
-
A.
foundedAsGuild
chosen
Indicates that an organization or institution was originally established in the form of a guild.
-
B.
craftGuild
Indicates that an entity is a member of, affiliated with, or governed by a particular craft guild organization.
-
C.
associatedCraftsmen
Indicates that there is a relationship linking an entity to one or more craftsmen who are connected to it through work, creation, or service.
-
D.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
E.
traditionalCraftCenter
Indicates that a place functions as a hub where traditional crafts are practiced, taught, preserved, or showcased.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 1:48 a.m.