Triple
T35990536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Thymbraeus |
E1040830
|
entity |
| Predicate | cultLocaleType |
P19051
|
FINISHED |
| Object | extra-urban sanctuary |
—
|
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: extra-urban sanctuary | Statement: [Apollo Thymbraeus, cultLocaleType, extra-urban sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultLocaleType Context triple: [Apollo Thymbraeus, cultLocaleType, extra-urban sanctuary]
-
A.
localeType
chosen
Indicates the classification or category of a locale (such as region, city, or venue type) that characterizes the kind of place involved in the relationship.
-
B.
locale
Indicates that one entity is the place, setting, or geographic area in which another entity exists, occurs, or is situated.
-
C.
languageOfSurroundingCulture
Indicates that one entity is the language predominantly used or characteristic of the surrounding culture associated with another entity.
-
D.
canonicalLanguage
Indicates that one entity is the officially recognized or standard language associated with another entity.
-
E.
regionLanguage
Indicates that a particular language is used or officially recognized within a specific geographic region.
- 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.