Triple
T20760890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beast Wars Scorponok |
E510971
|
entity |
| Predicate | beastModeType |
P141405
|
FINISHED |
| Object | mechanical scorpion |
—
|
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: mechanical scorpion | Statement: [Beast Wars Scorponok, beastModeType, mechanical scorpion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beastModeType Context triple: [Beast Wars Scorponok, beastModeType, mechanical scorpion]
-
A.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
B.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
C.
metricType
Indicates the specific category or kind of measurement that a given metric represents.
-
D.
redshiftType
Indicates the classification of an object's redshift according to how the redshift was determined or what type of redshift it represents.
-
E.
metadataType
Indicates that one entity specifies the kind or category of metadata associated with 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c248701081908ae49fca933e05f6 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:35 p.m.