Triple
T23996139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usama ibn Zayd |
E605193
|
entity |
| Predicate | commandedExpeditionTo |
P123304
|
FINISHED |
| Object | Balqa in the Levant |
—
|
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: Balqa in the Levant | Statement: [Usama ibn Zayd, commandedExpeditionTo, Balqa in the Levant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandedExpeditionTo Context triple: [Usama ibn Zayd, commandedExpeditionTo, Balqa in the Levant]
-
A.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
B.
issExpedition
Indicates an expedition or mission associated with the International Space Station (ISS).
-
C.
commandedForcesFrom
Indicates that one entity held command authority over military or organizational forces originating from another entity.
-
D.
commandedMission
Indicates that one entity served as the commanding leader or officer in charge of a particular mission carried out by another entity.
-
E.
organizedExpedition
chosen
Indicates that an entity planned, coordinated, and arranged the details of an expedition or journey.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d38f8a208190a293c64b9c9202c0 |
completed | April 29, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69f1615994c48190a5de95d3f7e5cd0a |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:38 p.m.