Triple
T33150207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Woman from Pontus |
E848413
|
entity |
| Predicate | relatedRegionInTitle |
P35463
|
FINISHED |
| Object | Pontus |
E64311
|
NE 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: Pontus | Statement: [The Woman from Pontus, relatedRegionInTitle, Pontus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedRegionInTitle Context triple: [The Woman from Pontus, relatedRegionInTitle, Pontus]
-
A.
regionalTitles
Indicates that an entity holds or is associated with titles or designations that are specific to particular geographic regions.
-
B.
associatedTitleTerritory
Indicates a relationship where a specific title is linked or connected to a particular territory or domain.
-
C.
mentionsRegion
chosen
Indicates that one entity explicitly refers to or cites a specific geographic region in its content or context.
-
D.
relatedTitleHolder
Indicates that one entity holds a title or position that is related or connected to the title or position held by another entity.
-
E.
associatedTitleLocation
Indicates a relationship where a title is linked to a specific location with which it is contextually or formally connected.
- F. None of above.
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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525bc4868819083b20bc3839649be |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:28 a.m.