Triple
T33003847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Management Consultants |
E844440
|
entity |
| Predicate | hasWorshipfulCompanyRank |
P195319
|
FINISHED |
| Object | 105 |
—
|
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: 105 | Statement: [Worshipful Company of Management Consultants, hasWorshipfulCompanyRank, 105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorshipfulCompanyRank Context triple: [Worshipful Company of Management Consultants, hasWorshipfulCompanyRank, 105]
-
A.
hasLiturgicalRank
Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
-
B.
hasClergyRankOver
Indicates that one clergy member holds a higher ecclesiastical rank or authority than another within a religious hierarchy.
-
C.
isOrderOfKnighthood
Indicates that an entity is a formal chivalric or knightly order to which individuals can be admitted.
-
D.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
E.
confersHonorificStatus
Indicates that one entity formally grants an honorific title, rank, or status to 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_69fdbaa1313081908beea28a5597ae40 |
completed | May 8, 2026, 10:27 a.m. |
Created at: May 1, 2026, 1:23 a.m.