Triple
T38087791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalikwanda |
E951019
|
entity |
| Predicate | transportedPerson |
P201303
|
FINISHED |
| Object | Litunga |
—
|
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: Litunga | Statement: [Nalikwanda, transportedPerson, Litunga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportedPerson Context triple: [Nalikwanda, transportedPerson, Litunga]
-
A.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
B.
transportedFor
Indicates that one entity was moved or carried from one place to another for the benefit, use, or purpose of another entity or activity.
-
C.
transportedObject
Indicates that an entity is the object being moved or carried from one location to another in a transport event.
-
D.
wasTransportedTo
Indicates that an entity was moved or carried from one location to another, resulting in its arrival at the specified destination.
-
E.
transportedAs
Indicates that one entity is moved or carried from one place to another in the form, role, or medium specified by another entity.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
| PDg | Predicate description generation | batch_69ffe6e21f748190a18dfe0878d397f7 |
completed | May 10, 2026, 2:01 a.m. |
Created at: May 3, 2026, 4:21 p.m.