Triple
T37962023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neandreia |
E947029
|
entity |
| Predicate | wasSynoecizedInto |
P124980
|
FINISHED |
| Object | Alexandria Troas |
—
|
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: Alexandria Troas | Statement: [Neandreia, wasSynoecizedInto, Alexandria Troas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSynoecizedInto Context triple: [Neandreia, wasSynoecizedInto, Alexandria Troas]
-
A.
laterSyncretizedWith
Indicates that one element was subsequently merged or conflated with another into a single, combined form or identity.
-
B.
wasUnifiedWith
Indicates that two or more previously separate entities were brought together to form a single unified whole.
-
C.
hasTerritoryReorganizedInto
chosen
Indicates that an entity’s territorial boundaries or administrative divisions have been restructured to form another specified territory.
-
D.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
-
E.
reunifiedAs
Indicates that entities which were previously separated or divided have been brought back together into a single unified whole.
- 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_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.