Triple
T31118258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Column of Phocas in the Roman Forum |
E793150
|
entity |
| Predicate | reusedElement |
P91997
|
FINISHED |
| Object | earlier Roman column shaft |
—
|
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: earlier Roman column shaft | Statement: [Column of Phocas in the Roman Forum, reusedElement, earlier Roman column shaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reusedElement Context triple: [Column of Phocas in the Roman Forum, reusedElement, earlier Roman column shaft]
-
A.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
B.
reusesStructureOf
Indicates that one entity adopts or incorporates the structural design or organization of another entity.
-
C.
partiallyReusedAs
Indicates that one entity is used again as part of another entity, but only to a limited or incomplete extent rather than in its entirety.
-
D.
notReusedFor
Indicates that something is not used again for a subsequent purpose, context, or instance.
-
E.
reusability
Indicates that an entity can be used multiple times or in multiple contexts without significant modification or degradation of function.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:04 p.m.