Triple
T4618217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colossus of Rhodes |
E100917
|
entity |
| Predicate | afterDestruction |
P56983
|
FINISHED |
| Object | remained lying on the ground for centuries |
—
|
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: remained lying on the ground for centuries | Statement: [Colossus of Rhodes, afterDestruction, remained lying on the ground for centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterDestruction Context triple: [Colossus of Rhodes, afterDestruction, remained lying on the ground for centuries]
-
A.
afterRelease
Indicates that one event, action, or state occurs subsequent to the release of another entity or condition.
-
B.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
C.
typeOfDestruction
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
D.
classAfter
Indicates that one class or course occurs later in time or sequence than another class or course.
-
E.
functionAfterDissolution
Indicates that one function, role, or operation occurs or continues after the dissolution or termination of another entity or structure.
- F. None of above. chosen
Provenance (4 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e247448190ad92f194cb1127c5 |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:12 p.m.