Triple
T13362485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polar Class 5 |
E318853
|
entity |
| Predicate | relativeStrengthRanking |
P96268
|
FINISHED |
| Object | stronger than Polar Class 6 |
—
|
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: stronger than Polar Class 6 | Statement: [Polar Class 5, relativeStrengthRanking, stronger than Polar Class 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeStrengthRanking Context triple: [Polar Class 5, relativeStrengthRanking, stronger than Polar Class 6]
-
A.
hasRelativeStrengthPosition
chosen
Indicates a comparative relationship where one entity’s strength is evaluated or ranked relative to another entity or a reference set.
-
B.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
-
C.
rankSignificance
Indicates how important or influential one entity is relative to others within a specified context or ordering.
-
D.
rankingImpact
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
-
E.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da628affd081909f1790d333f0eef4 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.