Triple
T38244031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endor |
E1013845
|
entity |
| Predicate | hasTechnologyPresence |
P198333
|
FINISHED |
| Object | primitive Ewok technology |
—
|
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: primitive Ewok technology | Statement: [Endor, hasTechnologyPresence, primitive Ewok technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTechnologyPresence Context triple: [Endor, hasTechnologyPresence, primitive Ewok technology]
-
A.
hasTechnologySystem
Indicates that one entity possesses, utilizes, or is supported by a particular technology system.
-
B.
hasTechnologyDomain
Indicates that an entity is associated with, operates within, or is relevant to a particular field or domain of technology.
-
C.
hasTechnologyTheme
Indicates that something is associated with, centers on, or prominently features technology as a primary theme or subject.
-
D.
hasTechnologyBasis
Indicates that something is founded upon, derived from, or fundamentally enabled by a particular technology.
-
E.
hasInteractiveTechnology
Indicates that an entity is equipped with or incorporates technology enabling user interaction or responsive engagement.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fedd5a5f4c8190acce88db56303703 |
completed | May 9, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_69fed910b31c8190ae837163d146738d |
completed | May 9, 2026, 6:49 a.m. |
| PDg | Predicate description generation | batch_69fedd5915588190bd884054e4be0414 |
completed | May 9, 2026, 7:08 a.m. |
Created at: May 3, 2026, 4:30 p.m.