Triple
T3664277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyber-King |
E77722
|
entity |
| Predicate | technologyOrigin |
P50245
|
FINISHED |
| Object | Cyberman 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: Cyberman technology | Statement: [Cyber-King, technologyOrigin, Cyberman technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyOrigin Context triple: [Cyber-King, technologyOrigin, Cyberman technology]
-
A.
technologyPioneered
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
B.
originallyDevelopedFor
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
C.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
D.
foundersOrigin
Indicates that the relationship specifies the geographic or cultural origin of the founders of an entity.
-
E.
placeOfDevelopment
Indicates the location where something (such as a product, project, or work) was created, designed, or developed.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3fe5eb08190ab15044acf9ac8a9 |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb97cdb788190a5ce96b21bd157ab |
completed | March 8, 2026, 6:01 p.m. |
Created at: March 8, 2026, 3:25 p.m.