Triple
T19587741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheikh Ibrahim ibn Abdallah |
E470146
|
entity |
| Predicate | aliasOfExplorer |
P136369
|
FINISHED |
| Object | Swiss explorer |
—
|
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: Swiss explorer | Statement: [Sheikh Ibrahim ibn Abdallah, aliasOfExplorer, Swiss explorer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliasOfExplorer Context triple: [Sheikh Ibrahim ibn Abdallah, aliasOfExplorer, Swiss explorer]
-
A.
associatedExplorer
Indicates a relationship where one entity is linked to or connected with an explorer, typically signifying that the explorer is relevant to, involved with, or responsible for that entity in some context.
-
B.
explorer
Indicates that an entity engages in the activity of exploring or investigating places, ideas, or domains.
-
C.
explorerDesignation
Indicates that an entity has been assigned a specific role, title, or status as an explorer.
-
D.
explorerClass
Indicates that an entity belongs to, or is categorized within, a particular class or type of explorer.
-
E.
coExplorer
Indicates that two or more entities jointly explore or investigate something together as partners.
- F. None of above. chosen
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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64052f61c81908bb49927d4246030 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:43 p.m.