Triple
T17924000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montanus |
E448143
|
entity |
| Predicate | geographicActivity |
P3227
|
FINISHED |
| Object | rural Phrygia |
—
|
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: rural Phrygia | Statement: [Montanus, geographicActivity, rural Phrygia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicActivity Context triple: [Montanus, geographicActivity, rural Phrygia]
-
A.
geographyBehavior
Indicates how an entity behaves, functions, or interacts in relation to its geographic context or location.
-
B.
activityLocation
Indicates the place or setting where an activity occurs or is carried out.
-
C.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
D.
geographicContext
chosen
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
E.
geographicalPractice
Indicates a relationship where an entity engages in or is associated with a practice, activity, or method that is specific to or characteristic of a particular geographic area or location.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30bde508190bc529ccae81f0e2a |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.