Triple
T3082810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busiris |
E64297
|
entity |
| Predicate | hasArchaeologicalRemainsOf |
P33395
|
FINISHED |
| Object | temples |
—
|
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: temples | Statement: [Busiris, hasArchaeologicalRemainsOf, temples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalRemainsOf Context triple: [Busiris, hasArchaeologicalRemainsOf, temples]
-
A.
hasArchaeologicalFeature
chosen
Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
-
B.
hasArchaeologicalExcavationsBy
Indicates that archaeological excavations at a site or location are or were conducted by a specified person, group, or organization.
-
C.
hasArchaeologicalValue
Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
-
D.
hasArchaeologicalSiteType
Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
-
E.
hasArchaeologicalCulture
Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e877008190aacbd6f1357bdb9b |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.