Triple
T14035584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monterozzi hill |
E337702
|
entity |
| Predicate | latestTombsDateTo |
P24460
|
FINISHED |
| Object | 2nd century BC |
—
|
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: 2nd century BC | Statement: [Monterozzi hill, latestTombsDateTo, 2nd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latestTombsDateTo Context triple: [Monterozzi hill, latestTombsDateTo, 2nd century BC]
-
A.
burialsUntil
Indicates the number of burial events that remain or are scheduled to occur up to a specified point in time or condition.
-
B.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
C.
latestTime
chosen
Indicates the most recent point in time at which the related event, state, or condition occurs or is valid among a set of possible times.
-
D.
eraOfMostBurials
Indicates the historical time period during which the greatest number of burials occurred for a given site or context.
-
E.
hasTombs
Indicates that one entity possesses, contains, or is the location of one or more tombs associated with another entity.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fac71188190a586049405f1071e |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.