Triple
T28408393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeginetan silver staters |
E719599
|
entity |
| Predicate | laterDesignChange |
P70881
|
FINISHED |
| Object | sea turtle replaced by land tortoise |
—
|
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: sea turtle replaced by land tortoise | Statement: [Aeginetan silver staters, laterDesignChange, sea turtle replaced by land tortoise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterDesignChange Context triple: [Aeginetan silver staters, laterDesignChange, sea turtle replaced by land tortoise]
-
A.
hasDesignChange
chosen
Indicates that an entity has undergone a modification or alteration to its original design.
-
B.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
-
C.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
D.
futureChangeRequires
Indicates that a planned or upcoming modification is contingent upon, or must be preceded by, another specified condition, action, or change.
-
E.
redesigned
Indicates that an entity has been modified or created anew in terms of its structure, appearance, or functionality, replacing a previous design.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 28, 2026, 1:25 a.m.