Triple
T1703662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Appia |
E36820
|
entity |
| Predicate | partiallyPreservedAs |
P2249
|
FINISHED |
| Object | archaeological site |
—
|
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: archaeological site | Statement: [Via Appia, partiallyPreservedAs, archaeological site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyPreservedAs Context triple: [Via Appia, partiallyPreservedAs, archaeological site]
-
A.
partiallyRecapturedBy
Indicates that an entity that was previously captured or controlled has been regained only in part by another entity, not fully restored to its prior captured state.
-
B.
partlyProtectedBy
Indicates that an entity is only partially safeguarded or covered by a specified protective measure, not fully protected.
-
C.
preservedExample
Indicates that an example instance has been kept intact or maintained in its original state for future reference or use.
-
D.
preservedAt
chosen
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
E.
partiallyCorrespondsTo
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
- 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_69a88617439c819094ffb5d16a0f6307 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab75ad24408190814069e6e3ef9e59 |
completed | March 7, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69aa61bad17c8190861b92cfb423f68f |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.