Triple
T1276214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sais |
E27217
|
entity |
| Predicate | archaeologicalRemainsInclude |
P19329
|
FINISHED |
| Object | temple ruins |
—
|
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: temple ruins | Statement: [Sais, archaeologicalRemainsInclude, temple ruins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologicalRemainsInclude Context triple: [Sais, archaeologicalRemainsInclude, temple ruins]
-
A.
archaeologicalFindsInclude
chosen
Indicates that the set of archaeological finds at a site or context contains or encompasses the specified items or types of artifacts.
-
B.
hasArchaeologicalValue
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
C.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
D.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
-
E.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c31602b8819087a57e8d390cae7a |
completed | March 1, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69a4bee0be808190a8ccac6a41851fdd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.