Triple
T1424088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cap of Maintenance |
E30288
|
entity |
| Predicate | hasUserRole |
P161
|
FINISHED |
| Object | heraldic officers |
—
|
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: heraldic officers | Statement: [Cap of Maintenance, hasUserRole, heraldic officers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserRole Context triple: [Cap of Maintenance, hasUserRole, heraldic officers]
-
A.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
B.
hasGlobalRole
Indicates that an entity holds a role or permission set that applies across an entire system or domain, rather than being limited to a specific scope or context.
-
C.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
D.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
E.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.