Triple
T16496747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comana in Pontus |
E400701
|
entity |
| Predicate | hasSanctuaryStatus |
P123779
|
FINISHED |
| Object | asylum |
—
|
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: asylum | Statement: [Comana in Pontus, hasSanctuaryStatus, asylum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSanctuaryStatus Context triple: [Comana in Pontus, hasSanctuaryStatus, asylum]
-
A.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
B.
isInSanctuaryWith
Indicates that two or more entities are located together within the same sanctuary or protected refuge at the same time.
-
C.
hasNewSanctuary
Indicates that an entity has acquired or established a new sanctuary location or protected refuge.
-
D.
hasOldSanctuary
Indicates that an entity possesses or is associated with an old or former sanctuary.
-
E.
hasSanctuaryName
Indicates that an entity is associated with or identified by a specific sanctuary name.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.