Triple
T3943580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thysdrus |
E92090
|
entity |
| Predicate | amphitheatrePreservationState |
P9592
|
FINISHED |
| Object | well-preserved |
—
|
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: well-preserved | Statement: [Thysdrus, amphitheatrePreservationState, well-preserved]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amphitheatrePreservationState Context triple: [Thysdrus, amphitheatrePreservationState, well-preserved]
-
A.
amphitheatreInstanceOf
Indicates that an entity is classified as, or is an instance of, an amphitheatre.
-
B.
stateOfPreservation
chosen
Indicates the condition or degree to which something has been maintained, conserved, or kept intact over time.
-
C.
heritageStatus
Indicates that an entity holds a particular cultural, historical, or natural heritage designation or protection status.
-
D.
monumentStatus
Indicates the official designation or condition of an entity as a monument, such as whether it is recognized, protected, or classified under heritage or preservation status.
-
E.
monumentState
Indicates that a monument is located within, or officially associated with, a particular state or state-level administrative region.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:24 p.m.