Triple
T29456452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zvartnots |
E747114
|
entity |
| Predicate | collapseCentury |
P167205
|
FINISHED |
| Object | 10th century |
—
|
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: 10th century | Statement: [Zvartnots, collapseCentury, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapseCentury Context triple: [Zvartnots, collapseCentury, 10th century]
-
A.
lostCentury
Indicates that a particular century or era has been forgotten, obscured, or is missing from records or collective knowledge.
-
B.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
C.
latestCentury
Indicates that the associated time or event occurs in, or belongs to, the most recent century relative to a given reference point.
-
D.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
-
E.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
- F. None of above. chosen
Provenance (4 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66b6cf8fc81909cd68959b362dde0 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3:46 p.m.