Triple
T33411339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTM322-01/9 |
E855590
|
entity |
| Predicate | familyPowerClass |
P186983
|
FINISHED |
| Object | approximately 2,100–2,400 shp |
—
|
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: approximately 2,100–2,400 shp | Statement: [RTM322-01/9, familyPowerClass, approximately 2,100–2,400 shp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPowerClass Context triple: [RTM322-01/9, familyPowerClass, approximately 2,100–2,400 shp]
-
A.
familyPowerBase
Indicates that an entity’s influence, authority, or control is derived primarily from its family connections or lineage.
-
B.
familyClass
Indicates that an entity belongs to, or is categorized within, a particular family grouping or class in a familial or taxonomic hierarchy.
-
C.
familyRank
Indicates the hierarchical position or status an entity holds within a family or kinship structure.
-
D.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
E.
familyType
Indicates the specific familial relationship or category that characterizes how the related entities are connected as family.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb2e9309fc81909dfefd9020d6fbad |
completed | May 6, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1:36 a.m.