Triple
T28563946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycian I |
E722620
|
entity |
| Predicate | hasPrimaryCorpusLocation |
P67055
|
FINISHED |
| Object | rock-cut tomb inscriptions in Lycia |
—
|
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: rock-cut tomb inscriptions in Lycia | Statement: [Lycian I, hasPrimaryCorpusLocation, rock-cut tomb inscriptions in Lycia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCorpusLocation Context triple: [Lycian I, hasPrimaryCorpusLocation, rock-cut tomb inscriptions in Lycia]
-
A.
hasPrimaryAssetLocation
Indicates that an entity’s main or principal asset is located at a specified place or facility.
-
B.
hasPartOfCorpus
chosen
Indicates that one entity constitutes a component or segment of the overall corpus associated with another entity.
-
C.
hasTermLocation
Indicates that a term or concept is associated with, or occurs at, a specific location.
-
D.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
E.
hasPrimaryLocationSetting
Indicates that an entity is associated with its main or default geographic or contextual 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: April 28, 2026, 4:06 a.m.