Triple
T37962026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neandreia |
E947029
|
entity |
| Predicate | regionDuringClassicalPeriod |
P41036
|
FINISHED |
| Object | Mysia |
—
|
NE NERFINISHED |
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: Mysia | Statement: [Neandreia, regionDuringClassicalPeriod, Mysia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDuringClassicalPeriod Context triple: [Neandreia, regionDuringClassicalPeriod, Mysia]
-
A.
countryDuringClassicalPeriod
Indicates that a specified country existed or is being considered in the context of the historical classical period.
-
B.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
-
C.
classicalContext
Indicates that the relationship or action occurs within, refers to, or is framed by a classical (e.g., ancient or traditional) cultural, historical, or stylistic context.
-
D.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
politicalStatusInClassicalPeriod
Indicates the political condition or standing an entity held during the classical historical period.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a007ef69f5c8190be6fb89e918d30fa |
completed | May 10, 2026, 12:49 p.m. |
| PD | Predicate disambiguation | batch_6a007e4060448190ad7420b07c1fe219 |
completed | May 10, 2026, 12:46 p.m. |
Created at: May 3, 2026, 4:20 p.m.