Triple
T3275066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Olympian Zeus |
E68737
|
entity |
| Predicate | spoliaUsedIn |
P37681
|
FINISHED |
| Object | later Byzantine and post-Byzantine buildings |
—
|
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: later Byzantine and post-Byzantine buildings | Statement: [Temple of Olympian Zeus, spoliaUsedIn, later Byzantine and post-Byzantine buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spoliaUsedIn Context triple: [Temple of Olympian Zeus, spoliaUsedIn, later Byzantine and post-Byzantine buildings]
-
A.
usesSpoliaFrom
chosen
Indicates that one entity incorporates or reuses building materials, decorative elements, or structural components taken from another, earlier structure or object.
-
B.
usedItem
Indicates that an entity has utilized or employed a particular item for some purpose.
-
C.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
wasUsedBy
Indicates that something served as a tool, resource, or means for an agent to perform an action or achieve a result.
-
E.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
- 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_69ad859b54f881909bf530d549caf2fd |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adaff8a440819092509bc8511b2785 |
completed | March 8, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69ada420167c81909b6e2702db296d9e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.