Triple
T12903307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Work-Related Activity Group |
E308664
|
entity |
| Predicate | hasLowerRateThan |
P61675
|
FINISHED |
| Object | Support Group |
—
|
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: Support Group | Statement: [Work-Related Activity Group, hasLowerRateThan, Support Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLowerRateThan Context triple: [Work-Related Activity Group, hasLowerRateThan, Support Group]
-
A.
hasLowerMonthlyPaymentThan
Indicates that one entity’s required monthly payment amount is less than that of another entity.
-
B.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
C.
hasLowerFrequencyIn
chosen
Indicates that one entity occurs or appears less frequently within a specified context than another entity.
-
D.
hasLowerCostPerBitThan
Indicates that the cost required to transmit or store each unit of data (bit) for one entity is lower than that for another entity.
-
E.
hasLower
Indicates that one entity is positioned at a lower level, rank, or value relative to another entity.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.