Triple
T35231058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria class |
E1017233
|
entity |
| Predicate | originClass |
P45791
|
FINISHED |
| Object | Upholder class |
E2130728
|
NE 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: Upholder class | Statement: [Victoria class, originClass, Upholder class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originClass Context triple: [Victoria class, originClass, Upholder class]
-
A.
classOrigin
chosen
Indicates the original class or category from which an entity is derived, instantiated, or classified.
-
B.
originalType
Indicates that one entity represents the initial or source type from which another entity is derived, transformed, or reclassified.
-
C.
destinationClass
Indicates the class or category that serves as the target or endpoint of a relationship or transition from another entity.
-
D.
originalExpansionClass
Indicates that one entity is the original or source class from which another entity has been expanded, derived, or extended.
-
E.
inspiredClass
Indicates that one class was conceived, designed, or implemented based on ideas, patterns, or structure taken from another class.
- F. None of above.
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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a380fa12968819091fc6e6b48faff49 |
completed | June 21, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.