Triple
T32790263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyages to Abyssinia |
E838606
|
entity |
| Predicate | settingNameUsed |
P15599
|
FINISHED |
| Object | Abyssinia |
—
|
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: Abyssinia | Statement: [Voyages to Abyssinia, settingNameUsed, Abyssinia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingNameUsed Context triple: [Voyages to Abyssinia, settingNameUsed, Abyssinia]
-
A.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
B.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
C.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
D.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
E.
usedAsSettingFor
chosen
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:14 a.m.