Triple
T35849162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aethiopia |
E1036299
|
entity |
| Predicate | appearsInSourceType |
P182361
|
FINISHED |
| Object | classical geography |
—
|
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: classical geography | Statement: [Aethiopia, appearsInSourceType, classical geography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInSourceType Context triple: [Aethiopia, appearsInSourceType, classical geography]
-
A.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
B.
usedInSourceType
Indicates that something is utilized or applied within a particular type or category of source.
-
C.
appearsFor
Indicates that one entity is presented, shown, or made visible on behalf of, or in representation of, another entity.
-
D.
mentionedInSourceType
chosen
Indicates that something is referenced or cited within a source of a particular type (e.g., book, article, website).
-
E.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:06 p.m.