Triple
T28663076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annexation of Pergamon |
E725517
|
entity |
| Predicate | statusBefore |
P26849
|
FINISHED |
| Object | independent Hellenistic kingdom |
—
|
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: independent Hellenistic kingdom | Statement: [Annexation of Pergamon, statusBefore, independent Hellenistic kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBefore Context triple: [Annexation of Pergamon, statusBefore, independent Hellenistic kingdom]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
statusBefore2022
Indicates that an entity’s status or condition is defined as it existed prior to the year 2022.
-
C.
earlierStatus
chosen
Indicates that one status or condition occurred or was valid before another status in time.
-
D.
legalStatusBefore
Indicates the legal condition or classification that applied to an entity prior to a specified event, change, or point in time.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: April 28, 2026, 4:59 a.m.