Triple
T8498341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | podrace on Tatooine |
E201152
|
entity |
| Predicate | technologyDepicted |
P50242
|
FINISHED |
| Object | repulsorlift engines |
—
|
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: repulsorlift engines | Statement: [podrace on Tatooine, technologyDepicted, repulsorlift engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyDepicted Context triple: [podrace on Tatooine, technologyDepicted, repulsorlift engines]
-
A.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
-
D.
technologyPresent
chosen
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
E.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe583aebc819090345684bfa1fca2 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.