Triple
T33003979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Security Professionals |
E844443
|
entity |
| Predicate | usesHallOf |
P175897
|
FINISHED |
| Object | other City of London livery companies |
—
|
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: other City of London livery companies | Statement: [Worshipful Company of Security Professionals, usesHallOf, other City of London livery companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesHallOf Context triple: [Worshipful Company of Security Professionals, usesHallOf, other City of London livery companies]
-
A.
inHallOfFame
Indicates that an entity has been formally inducted into a recognized Hall of Fame.
-
B.
hasHallOfFameParent
Indicates that an entity has a parent who is a member of a Hall of Fame.
-
C.
hasHallFunction
Indicates that an entity serves as or includes a hall used for gatherings, events, or similar functions.
-
D.
hasGrandHall
Indicates that an entity possesses or includes a grand hall as part of its structure or facilities.
-
E.
hasHallOfResidence
Indicates that an institution or organization provides or is associated with a specific hall of residence for accommodation.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:23 a.m.