Triple
T21786640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mramorje necropolis at Perućac |
E537853
|
entity |
| Predicate | hasLatestDate |
P23891
|
FINISHED |
| Object | 16th 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: 16th century | Statement: [Mramorje necropolis at Perućac, hasLatestDate, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatestDate Context triple: [Mramorje necropolis at Perućac, hasLatestDate, 16th century]
-
A.
hasLatestArtDate
Indicates the most recent date on which art associated with an entity was created, updated, or recorded.
-
B.
hasDateWith
Indicates that one entity is scheduled to go on or is engaged in a romantic or social date with another entity.
-
C.
latestPossibleDate
chosen
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
D.
hasOldestUnit
Indicates that one entity possesses or is associated with another entity that is the oldest unit within a specified group or hierarchy.
-
E.
hasBaseDate
Indicates that an entity is associated with a specific reference or starting date used as the basis for related calculations, schedules, or validity periods.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0621b5d6881908b74bc999c94fa3d |
completed | April 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:52 p.m.