Triple
T37827609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citadels |
E943107
|
entity |
| Predicate | supportsHiddenRoles |
P200590
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Citadels, supportsHiddenRoles, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHiddenRoles Context triple: [Citadels, supportsHiddenRoles, true]
-
A.
hasHiddenDesignationRole
chosen
Indicates that an entity holds a designation-related role that is concealed or not visible in the standard or public representation of roles.
-
B.
includesRoles
Indicates that one entity contains or encompasses one or more specified roles within its scope or structure.
-
C.
HideRole
Indicates that one entity conceals, suppresses, or makes another entity’s role or function not visible or known.
-
D.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
E.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.