Triple
T37873977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Enclave |
E944671
|
entity |
| Predicate | isSanctuary |
P123779
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Silver Enclave, isSanctuary, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSanctuary Context triple: [Silver Enclave, isSanctuary, yes]
-
A.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
B.
hasSanctuaryStatus
chosen
Indicates that an entity is officially designated or recognized as a sanctuary, enjoying a protected or special status.
-
C.
isInSanctuaryWith
Indicates that two or more entities are located together within the same sanctuary or protected refuge at the same time.
-
D.
hasSanctuaryIn
Indicates that an entity maintains or possesses a sanctuary located within a specified place or region.
-
E.
isLinkedToSanctuary
Indicates that an entity has a connection or association with a sanctuary, such as being related, directed, or assigned to it.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.