Triple
T21858253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yenisei inscriptions |
E539688
|
entity |
| Predicate | contentFeatures |
P80690
|
FINISHED |
| Object | personal names |
—
|
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: personal names | Statement: [Yenisei inscriptions, contentFeatures, personal names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentFeatures Context triple: [Yenisei inscriptions, contentFeatures, personal names]
-
A.
featuresIn
chosen
Indicates that an entity appears or plays a role within another entity, such as a person or element being included in a work, event, or context.
-
B.
featuredContentType
Indicates the specific type or category of content that is highlighted or promoted as featured.
-
C.
contentIs
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
D.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
-
E.
mediaFeature
Indicates a characteristic, capability, or attribute of a media item that distinguishes how it is presented, functions, or is experienced.
- 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_69e0c47829648190bbe2d1d7033768ec |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0d638721c8190918fc6ad9c5d5bf6 |
completed | April 28, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:56 p.m.