Triple
T35892565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Thymbraeus |
E1038123
|
entity |
| Predicate | cultLocationType |
P9995
|
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, cultLocationType, extra-urban sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultLocationType Context triple: [Apollo Thymbraeus, cultLocationType, extra-urban sanctuary]
-
A.
cultLocation
chosen
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
B.
placeType
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
C.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
-
D.
cityTypeLocation
Indicates that a location is classified as a specific type of city (e.g., capital, metropolitan, coastal).
-
E.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
- 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_69f76e2190f88190beb2eed798a4ef01 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa3b4914819098a40400cf7f5b31 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d435288190b30b1991fb003121 |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.