Triple
T35561846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impero |
E1027654
|
entity |
| Predicate | designedShafts |
P199117
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Impero, designedShafts, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedShafts Context triple: [Impero, designedShafts, 4]
-
A.
hasShafts
Indicates that one entity possesses or is equipped with one or more shafts as components or structural elements.
-
B.
propulsionShafts
Indicates a relationship where shafts are used to transmit mechanical power for propulsion between components of a system.
-
C.
shaftArrangement
Indicates how one or more shafts are positioned, oriented, or configured relative to each other within a mechanical or structural system.
-
D.
typicalShaftType
Indicates the usual or characteristic type of shaft associated with an entity or configuration.
-
E.
shaftFeature
Indicates a relationship where one object possesses or is characterized by a shaft-like structural feature.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
| PDg | Predicate description generation | batch_69ff1f3ee3588190a857d1504c93be8b |
completed | May 9, 2026, 11:49 a.m. |
Created at: May 3, 2026, 4:04 p.m.