Triple
T34982054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trabe |
E1008840
|
entity |
| Predicate | technologyComparedToKazon |
P116408
|
FINISHED |
| Object | more advanced |
—
|
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: more advanced | Statement: [Trabe, technologyComparedToKazon, more advanced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyComparedToKazon Context triple: [Trabe, technologyComparedToKazon, more advanced]
-
A.
technologyComparableTo
Indicates that one technology can be meaningfully compared to another in terms of capability, performance, or relevant characteristics.
-
B.
technologyLevelComparedTo
chosen
Indicates how the technological advancement of one entity compares relative to that of another entity.
-
C.
comparisonSystem
Indicates a relationship where one entity serves as the system, framework, or method used to compare or evaluate another entity.
-
D.
technologyCounterpartOf
Indicates a relationship where one technology serves as an equivalent, alternative, or corresponding counterpart to another technology.
-
E.
technologyLevelComparedToPredecessor
Indicates how the technology level of an entity compares to that of its immediate predecessor.
- F. None of above.
Provenance (3 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.