Triple
T19961038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC |
E479813
|
entity |
| Predicate | higherCategoryComparedTo |
P138038
|
FINISHED |
| Object | TLK |
—
|
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: TLK | Statement: [IC, higherCategoryComparedTo, TLK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: higherCategoryComparedTo Context triple: [IC, higherCategoryComparedTo, TLK]
-
A.
highestCategory
Indicates that the related entity is the topmost or most specific category to which another entity is ultimately classified or assigned.
-
B.
higherRankHas
Indicates that one entity holds a higher rank or hierarchical position than another entity.
-
C.
higherValueIndicates
Indicates that a greater numerical or qualitative value of one entity corresponds to a stronger presence, importance, or intensity of a specified property or outcome relative to another.
-
D.
higherRankDescription
Indicates that one entity holds a superior or more senior rank or status compared to another entity.
-
E.
comparisonLevel
Indicates the degree or intensity to which two or more entities are being compared within a given context.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.