Triple
T33026176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | crossing of the Rub' al Khali |
E845048
|
entity |
| Predicate | mainExplorer |
P45899
|
FINISHED |
| Object | Wilfred Thesiger |
—
|
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: Wilfred Thesiger | Statement: [crossing of the Rub' al Khali, mainExplorer, Wilfred Thesiger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainExplorer Context triple: [crossing of the Rub' al Khali, mainExplorer, Wilfred Thesiger]
-
A.
explorer
Indicates that an entity engages in the activity of exploring or investigating places, ideas, or domains.
-
B.
coExplorer
Indicates that two or more entities jointly explore or investigate something together as partners.
-
C.
associatedExplorer
chosen
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.
-
D.
aliasOfExplorer
Indicates that one entity is an alternative name, nickname, or alias used for a particular explorer.
-
E.
explorerNumber
Indicates the numerical identifier assigned to an explorer within a given context or system.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:23 a.m.